Data safe

ABSTRACT

The disclosure facilitates creating and using a data safe for user personal information via creating block chains of personal information in a distributed file system (DFS), based on a determined category of use of each of the block chains, and/or transmitting an authorization to access a set of the block chains based on the determined category of use associated with a request for authorization. The disclosure also facilitates storing machine-executable code associated with an offer, wherein the block chains are based on a determined category of use of personal information in the block chains, determining the determined category of use of personal information, and/or transmitting a request for authorization to access personal information and the determined category of use associated with the request for authorization, receiving a cryptographic hash associated with a last block of a block chain and a link to the block chain stored in DFS.

This patent application is a continuation of U.S. patent applicationSer. No. 16/555,800, filed Aug. 29, 2019, entitled “DATA SAFE,” whichclaims priority to U.S. Provisional Patent Application Ser. No.62/724,989, filed Aug. 30, 2018, entitled “DATA SAFE,” whichapplications are incorporated by reference herein in their entireties.

TECHNICAL FIELD

The subject disclosure is directed to software applications and servicesand, more specifically, relates to data storage, use, protection, andauthorization, such as by algorithms, methods, and platforms that enablecreating, managing, authorizing the use of, and using user data in adistributed, secure, and controlled fashion.

BACKGROUND

Public and private entity data breaches are now an accepted, ifunfortunate, aspect of modern life. Once a user's data security becomescompromised, it is a difficult if not impossible situation to rectify.More generally, users have come to expect a certain level ofavailability, use, and/or perceived misuse of their personalinformation. Identity theft costs victims on the order of $15 billionper year, in addition to lost time, loss of productivity, reduced trust,and personal well-being. Moreover, identity theft can negatively impactcredit scores, further exacerbating the impacts, as a result ofincreased credit costs, and can result in increased fraud prevention andprotection costs for entities.

Unfortunately, conventional solutions focus primarily on treating thesymptoms, rather than the causes, and/or they may introduce furthercosts of doing business in a modern digital world. For example, in theevent of identity theft or a data breach, a standard solution is tooffer credit monitoring or to lock a user's credit. These costs may beborne by the institution that was initially victimized in the databreach, or more broadly by taxpayers in the event of a public entitydata breach, in addition to increased processing time and/or user effortrequired to conduct further business, for example, such as in making oranswering inquiries about the identity theft or breach.

Furthermore, such conventional solutions may be inappropriate and/orinadequate to address user concerns over use and/or misuse of userinformation, for example, such as in the situation where a user hasprovided user information to a first entity, subject to an end userlicense agreement (EULA), but where the user would prefer that use ofsuch user information is restricted. For example, a user might agree toa EULA that allows a first entity uses of such user information beyondthat which the user contemplates, only to find out subsequently thattheir information is being used in a manner in which they object, ifthey had conceived of such usage at the time they agreed to the EULA.For instance, social media companies are increasingly facing user pushback for the ways in which political organizations, accessed their userinformation. In such situations, there is no breach or identity theft,however, the user has no control over which information is shared and/orthe manner in which it is being used.

Moreover, there exists an opportunity to streamline the conduct ofdigital business, which can create heretofore unseen efficiencies forusers and businesses in the conduct of ordinary businesses. For example,every entity has particular forms, layouts, schedules of data that theyrequire, in order to conduct business. For example, a prospectiveemployer requires particular employment history and right to workcredentials, such as an social security number or individual taxpayeridentification number, in addition to basic personal identificationinformation. A medical service provider may require a subset of suchinformation as well as other information not applicable to theprospective employer. An insurer might require subsets of both as all aswell as other information not applicable to either the prospectiveemployer or the medical service provider.

Conventionally, a user provides each in turn, separately filling outrequired forms, duplicating efforts, potentially making errors ofomission, or otherwise, and keeping the required records or listings ofdetails, making return trips or efforts to ensure all pertinent detailsare provided. For its part, each entity is responsible for verifying theuser details and data completeness, screening for fraud, eligibility,risk, etc., in order to meet the entity business goals and specifiedprocesses. All of these duplicative and time consuming efforts raise addup to a cost of doing business, especially in an era when public andprivate entity data breaches are now an accepted, if unfortunate, aspectof modern life.

Thus, while conventional processes for handling user information and/orsolutions for misuse or potential misuse provide some measure ofsecurity, user control, and/or rectification for data breaches, suchefforts fail to provide meaningful solutions for increased user controland/or security of user information, and/or are subject to further costsor drawbacks, etc., among other deficiencies. The above-describeddeficiencies of user data provision and security are merely intended toprovide an overview of some of the problems of conventional systems andmethods, and are not intended to be exhaustive. Other problems withconventional systems and corresponding benefits of the variousnon-limiting embodiments described herein may become further apparentupon review of the following description.

SUMMARY

The following presents a simplified summary of the specification toprovide a basic understanding of some aspects of the specification. Thissummary is not an extensive overview of the specification. It isintended to neither identify key or critical elements of thespecification nor delineate any scope particular to any embodiments ofthe specification, or any scope of the claims. Its sole purpose is topresent some concepts of the specification in a simplified form as aprelude to the more detailed description that is presented later.

Thus, in non-limiting embodiments, the disclosed subject matter relatesto software and services and, more specifically, relates to software andservices that facilitate creating and using a data safe for userpersonal information, and so on. In one non-limiting aspect, thedisclosed subject matter can comprise storing personal informationassociated with a user in a distributed file system (DFS). In furthernon-limiting aspects, the disclosed subject matter can comprise creatingblock chains of personal information, based on a determined category ofuse of each of the block chains. In still further non-limiting aspects,the disclosed subject matter can comprise transmitting an authorizationto access a set of the block chains based on the determined category ofuse associated with a request for authorization.

To the foregoing and related ends, systems, devices, and methods aredisclosed that can facilitate creating and using a data safe for userpersonal information according to various aspects of the disclosedsubject matter, among other related functions. For instance, accordingto various non-limiting embodiments, the disclosed subject matter cancomprise a storage component configured to store personal informationassociated with a user in a distributed file system (DFS). According tofurther non-limiting implementations, the disclosed subject matter cancomprise a data management component configured to create block chainsof personal information, based on a determined category of use of eachof the plurality of block chains. According to still furthernon-limiting implementations, the disclosed subject matter can comprisean authorization component configured to transmit an authorization toaccess a set of the block chains based on the determined category of useassociated with a request for authorization.

In addition, non-limiting embodiments of the disclosed subject mattercan provide exemplary methods that facilitate creating and using a datasafe for user personal information. For example, in further non-limitingimplementations, exemplary methods can comprise storingmachine-executable code associated with an offer, wherein the offer iscontingent upon access to personal information stored in a set of blockchains, wherein the block chains are based on a determined category ofuse of personal information in the block chains, determining thedetermined category of use of personal information, transmitting arequest for authorization to access personal information and thedetermined category of use associated with the request forauthorization, receiving a cryptographic hash associated with a lastblock of a block chain and a link to the block chain stored in DFS.

In other non-limiting embodiments, the disclosed subject matter cancomprise a storage component configured to store machine-executable codeassociated with an offer, wherein the offer is contingent upon access topersonal information stored in block chains, wherein the block chainsare based on a determined category of use of personal information ineach of the block chains. According to further non-limitingimplementations, the disclosed subject matter can comprise a datamanagement component configured to determine the determined category ofuse of personal information. According to still further non-limitingimplementations, the disclosed subject matter can comprise anauthorization component configured to transmit a request forauthorization to access personal information and the determined categoryof use associated with the request for authorization, wherein theauthorization component is further configured to a cryptographic hashassociated with a last block of a block chain and a link to the lastblock of the block chain stored in DFS.

In addition, further exemplary implementations are directed to otherexemplary methods, and associated systems, devices and/or other articlesof manufacture that facilitate creating and using a data safe for userpersonal information, as further detailed herein.

These and other features of the disclosed subject matter are describedin more detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The devices, components, systems, and methods of the disclosed subjectmatter are further described with reference to the accompanying drawingsin which:

FIG. 1 depicts a functional block diagram illustrating an exemplaryenvironment suitable for use with aspects of the disclosed subjectmatter;

FIG. 2 illustrates an exemplary block diagram showing non-limitingaspects of embodiments of the disclosed subject matter;

FIG. 3 illustrates an exemplary block diagram showing furthernon-limiting aspects of embodiments of the disclosed subject matter;

FIG. 4 illustrates non-limiting examples of user information about auser that can be employed in the provision, collection, use,distribution, and so on, of user information about the user, inaccordance with various embodiments of an exemplary data safe or userdata safe;

FIG. 5 illustrates an exemplary flow diagram of methods directed tocreation of user information or data block chains according non-limitingaspects of embodiments of the disclosed subject matter;

FIGS. 6-14 illustrates flow diagrams of non-limiting aspects ofexemplary processes for creation of user information or data blockchains according non-limiting aspects of embodiments of the disclosedsubject matter;

FIG. 15 illustrates an exemplary flow diagram of methods directed to ause of user information or data block chains according non-limitingaspects of embodiments of the disclosed subject matter;

FIG. 16 illustrates another flow diagram of further non-limiting aspectsof exemplary methods for using user information or data block chainsaccording non-limiting aspects of embodiments as disclosed herein;

FIGS. 17-19 illustrates flow diagrams of non-limiting aspects ofexemplary processes for use of user data block chains accordingnon-limiting aspects of embodiments of the disclosed subject matter;

FIG. 20 depicts a functional block diagram illustrating exemplarynon-limiting devices or systems suitable for use with aspects of thedisclosed subject matter;

FIG. 21 illustrates an overview of an exemplary computing environmentsuitable for incorporation of embodiments of the disclosed subjectmatter;

FIG. 22 depicts an exemplary non-limiting device or system suitable forperforming various aspects of the disclosed subject matter;

FIG. 23 illustrates an exemplary non-limiting device or system suitablefor performing various aspects of the disclosed subject matter

FIG. 24 is a block diagram representing exemplary non-limiting networkedenvironments in which various embodiments described herein can beimplemented;

FIG. 25 is a block diagram representing an exemplary non-limitingcomputing system or operating environment in which one or more aspectsof various embodiments described herein can be implemented; and

FIG. 26 illustrates a schematic diagram of an exemplary mobile device(e.g., a mobile handset) that can facilitate various non-limitingaspects of the disclosed subject matter in accordance with theembodiments described herein.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

As described above, conventional processes for handling user informationand/or solutions for misuse or potential misuse provide some measure ofsecurity, user control, and/or rectification for data breaches, suchefforts fail to provide meaningful solutions for increased user controland/or security of user information, and/or are subject to further costsor drawbacks, etc., among other deficiencies.

FIG. 1 depicts a functional block diagram illustrating an exemplaryenvironment 100 suitable for use with aspects of the disclosed subjectmatter. For instance, depicts an exemplary set of parties orparticipants communicatively coupled to each other and involved in theprovision, collection, use, and distribution of user information. Forexample, a user 102 can provide information to other parties, forexample, such as data provider(s) 104 and data consumer(s) 106. Asanother example, data provider(s) 104 and/or data consumer(s) 106 cancomprise or be associated with data source(s) 108 and/or verifyingentities 110, to facilitate the provision of information about user 102,according to data provider(s)' 104 business structures and models, andto facilitate the consumption of information about user 102, accordingto data consumer(s)' 106 business structures and models.

As a non-limiting example, data consumer 106 can comprise a prospectiveemployer for which it seeks user information about user 102. In thisnon-limiting example, user 102 comprise a prospective employee, and aspart of the prospective employer's business processes, data consumer(s)106 would require the submission of user information by user 102 in theform of a job application package. In addition, data consumer 106 maycontract with other participants, including one or more of dataprovider(s) 104, data source(s) 108, and/or verifying entities 110. Forinstance, one or more of data provider(s) 104, data source(s) 108,and/or verifying entities 110 can be associated with credit reportingentities, other rating entities, background check entities, employmentverification, government agencies, depending on various businessstructures or models, with which data consumer 106 may contract orcommunicate with to facilitate the consumption of information about user102, according to data consumer's 106 business processes and hiringgoals.

As described above, beyond the basic job application submission processuser 102 has little no control over the provision, collection, use, anddistribution of user information about user 102, other than a take it orleave it approach to whatever policy is in place with data consumer 106.In addition, the retention of such information by data consumer 106leaves user 102 relatively helpless to prevent against data breachesand/or any subsequent identity theft or misuse of such user information.Moreover, each prospective employer, e.g., data consumer 106, may haveits own user information requirements, retention policies, privacypolicies, and so on, as further exacerbates the problems of efficientlyproviding such user information, controlling the proliferation thereof,and protecting against data breaches, which further complicates effortsat achieving efficiencies in the proper or authorized provision,collection, use, and distribution of user information about user 102.

Various embodiments of the disclosed subject matter facilitate creatingand using a data safe or user data safe 112 for user information or userpersonal information, as further described herein. Non-limitingembodiments of data safe or user data safe 112 as described herein canfacilitate enhanced user 102 control over the provision, collection,use, distribution, and so on, of user information about user 102 and canfacilitate providing further benefits from achieving efficiencies in theproper or authorized provision, collection, use, distribution, and soon, of user information about user 102. For instance, rather than eachof data consumer(s) 106 being required to separately form likelydifferent policies, processes, and infrastructure for the provision,collection, use, and/or distribution of user information about user 102,being required to verify or authenticate such pieces of user informationabout user 102, and/or being required to form and/or managerelationships between data consumer(s) 106 and one or more of dataprovider(s) 104, data source(s) 108, and/or verifying entities 110, tofacilitate the provision, collection, use, and/or distribution of userinformation about user 102, each of data consumer(s) 106 can becommunicatively coupled to data safe or user data safe 112 to facilitatethe provision, collection, use, and/or distribution of user informationabout user 102, in various embodiments as described herein.

As indicated in FIG. 1, and as further described herein, one or more ofdata provider(s) 104, data source(s) 108, and/or verifying entities 110can be communicatively coupled to the data safe or user data safe 112 tofacilitate the provision, collection, use, distribution, and so on, ofuser information about user 102, according to their respective businessstructures and models. Thus, the traditional roles of such participantscan be preserved, while allowing further opportunities to facilitate theprovision, collection, use, distribution, and so on, of user informationabout user 102. As a non-limiting example, exemplary data safe or userdata safe 112 can comprise an application program interface (API) and/orone or more management mechanisms to facilitate controlling which dataconsumer(s) 106 may access user information about user 102 via exemplarydata safe or user data safe 112. In other non-limiting implementations,exemplary data safe or user data safe 112 can comprise or be associatedwith functionality for the provision of self-executing contracts, whichcan, on behalf of one or more participants in exemplary environment 100,facilitate the provision, collection, use, distribution, and so on, ofuser information about user 102. Such self-executing contracts may beimplemented as, for example, software contracts in the manner of smartcontracts on a block chain such as the Ethereum block chain or similarblock chains that permit the implementation of self-executing contracts.

As described above, an exemplary user 102 can comprise an individualhuman person, properly authorized and authenticated to use data safe oruser data safe 112 to facilitate the provision, collection, use,distribution, and so on, of user information about user 102, and/or oneor more computer-executable components acting on behalf of exemplaryuser 102. However, in other non-limiting implementations, exemplary user102 can comprise any of a number of real or intangible entities aboutwhich user information is desired by one or more data consumer(s) 106.As non-limiting examples, exemplary user 102 can comprise any of aperson, an entity, an organization, a legal structure (e.g., trusts,etc.), or otherwise, without limitation, about which user informationabout user 102 is desired by one or more data consumer(s) 106. Asfurther described above, exemplary data consumer(s) 106 can compriseprospective employers. In further non-limiting implementations,exemplary data consumer(s) 106 can comprise any of a number of entitiesthat desire user information about user 102, including a serviceprovider, whether online or otherwise, such as a cell phone provider, ahealth care provider such as a doctor, a merchant such as an automobiledealer, a rental agency, an insurance firm, a governmental organizationsuch as a school, a tax authority, other users 102, and so on, withoutlimitation.

As indicated in FIG. 1, one or more of data provider(s) 104, datasource(s) 108, and/or verifying entities 110 can be communicativelycoupled to the data safe or user data safe 112 to facilitate theprovision, collection, use, distribution, and so on, of user informationabout user 102, according to their respective business structures andmodels. Accordingly, exemplary data provider(s) 104 can comprise any ofa number of entities whose mission or business involves or is associatedwith one or more of the provision, collection, use, distribution, and soon, of user information about user 102, such as, for example, a ratingsagency, such as a credit rating agency, a background check agency, apolling firm, a marketing firm, a government agency, and so on, withoutlimitation, an actuarial firm, without limitation. In furthernon-limiting aspects, exemplary data source(s) 108 can comprise any of anumber of data sources from which user information about user 102 may beaccessed, whether public or private, whether freely accessible orfee-based, whether governmental or private-owned, whether automated orotherwise, and so on without limitation. In other non-limiting aspects,exemplary verifying entities 110 can comprise any of a number ofentities whose mission or business involves or is associated with thevalidation or verification of user information about user 102 tofacilitate one or more of the provision, collection, use, distribution,and so on, of user information about user 102, such as, for example, aratings agency, such as a credit rating agency, a background checkagency, a certification authority, an authentication entity, and so onwithout limitation.

As described above, in a non-limiting aspect, one or morecomputer-executable components can act on behalf of exemplary user 102in exemplary data safe or user data safe 112. Similarly, in furthernon-limiting aspects, one or more computer-executable components can acton behalf of one or more of data provider(s) 104, data source(s) 108,and/or verifying entities 110 in association with the data safe or userdata safe 112 to facilitate the provision, collection, use,distribution, and so on, of user information about user 102, accordingto their respective business structures and models.

FIG. 2 illustrates an exemplary block diagram 200 showing non-limitingaspects of embodiments of the disclosed subject matter. For instance,block diagram 200 depicts activities or events associated with a user orcustomer (e.g., user 102) in the life cycle of an interaction of theuser or customer (e.g., user 102) with an institution, business, etc.(e.g., data consumer 106). These activities or events rely heavily, notonly on the provision, collection, use, distribution, and so on, of userinformation about user 102, but they also rely on the validation,verification, authentication, and proper protection and control of suchuser information about user 102, to ensure smooth, efficient, andcost-effective business processes, and therefore, in turn, attractiveprices on the offered goods and services.

While for purposes of illustration, FIG. 2 is discussed in terms of anexemplary credit lending process, it is understood that that variousembodiments as described herein are not so limited. For instance,similar analyses regarding a medical service provider and his or herpatient, regarding an employer and his or her employee, regarding aninsurer and his or her insured, and so on can be performed and revealsimilar opportunities to improve the provision, collection, use,distribution, and so on, of user information about user 102, as well asthe validation, verification, authentication, and proper protection andcontrol of such user information about user 102.

As a non-limiting example, from the perspective of an exemplary user orcustomer (e.g., user 102), in terms of Prospect Targeting 202, userinformation about user or customer (e.g., user 102) may be solicited,provided, collected, used, distributed, and so on, to determine one ormore of a product qualification process, a study of in-marketpropensity, determination of proper or most efficient contactchannel(s), effective messaging technologies or techniques, optionalproduct offering(s), timing of offers, intensity of contacts, characterof messaging including pre-approvals versus invitations to apply, and soon associated with exemplary user or customer (e.g., user 102).

In terms of Know Your Customer 204, user information about user orcustomer (e.g., user 102) may be solicited, provided, collected, used,distributed, and so on, to determine the existence of synthetic identityrisks, for the verification and/or authentication of identities andcredentials employed therefor, compliance with regulatory schemes (e.g.,Gramm-Leach-Bliley Act, U.S.A. Patriot Act, etc.), and so on associatedwith exemplary user or customer (e.g., user 102).

Regarding the Application Decision 206, user information about user orcustomer (e.g., user 102) may be solicited, provided, collected, used,distributed, and so on, to determine, track, prevent, and/or mitigateone or more of repayment risk, bankruptcy, loss severity, such as bydetermining or verifying, ability to pay, income, employment, employingconditional approvals (e.g., with terms attached), and so on associatedwith exemplary user or customer (e.g., user 102).

In terms of Fraud Prevention 208, user information about user orcustomer (e.g., user 102) may be solicited, provided, collected, used,distributed, and so on, to determine, track, prevent, and/or mitigatefirst party fraud (e.g., lack of intent to repay, bust-out), third partyfraud (e.g., identity theft, synthetic identity), and so on associatedwith exemplary user or customer (e.g., user 102).

Regarding Underwriting/Onboarding 210, user information about user orcustomer (e.g., user 102) may be solicited, provided, collected, used,distributed, and so on, to determine one or more of offer pricing, offerterms, opportunities to cross-sell and/or up-sell, lifetime value of theoffer, possible product add-ons, and so on associated with exemplaryuser or customer (e.g., user 102).

In terms of Account Management 212, user information about user orcustomer (e.g., user 102) may be solicited, provided, collected, used,distributed, and so on, to determine the value of an offered creditline, possibility for and risk associated with increases or decreases,over limit authorization, retention, usage, opportunities for cross-selland/or up-sell, existence of account takeover fraud events, existence ofaccount bust-out fraud likelihood or events, and so on associated withexemplary user or customer (e.g., user 102).

Regarding Debt Management 214, user information about user or customer(e.g., user 102) may be solicited, provided, collected, used,distributed, and so on, to determine internal considerations of thepossibility of early account collections, external considerations ofearly collections such as pricing and agency selection, the likelihoodor preventative measures for repossession and/or foreclosure, and so onassociated with exemplary user or customer (e.g., user 102).

All of such activities or events of block diagram 200 associated withuser or customer (e.g., user 102) incur some costs of the provision,collection, use, distribution, and so on, of user information about user102, as well as with the validation, verification, authentication, andproper protection and control of such user information about user 102,to ensure smooth, efficient, and cost-effective business processes. Forexample, from the perspective of an exemplary data consumer 106, interms of Prospect Targeting 202, availability, costs, efficiencies, etc.regarding user information associated with exemplary user or customer(e.g., user 102) can be useful in efficiently determining one or more ofbudget, product mix, capabilities, portfolio quality, and so onassociated with exemplary data consumer 106.

In terms of Know Your Customer 204, user information about user orcustomer (e.g., user 102) solicited, provided, collected, used,distributed, and so on, as well as costs and efficiencies therewith canfacilitate efficiently satisfying regulatory requirements, setting staffbudgets, determining turndown rates, and so on associated with exemplarydata consumer 106.

In terms of Application Decision 206, user information about user orcustomer (e.g., user 102) solicited, provided, collected, used,distributed, and so on, as well as costs and efficiencies therewith canfacilitate efficiently determining portfolio quality, approval rate,Basel standards (e.g., loss given default, exposure at default, etc.,),etc., improving customer experiences, and so on associated withexemplary data consumer 106.

Regarding Fraud Prevention 208, user information about user or customer(e.g., user 102) solicited, provided, collected, used, distributed, andso on, as well as costs and efficiencies therewith can facilitateefficiently determining exposure or risk of fraud, turndown rates, staffbudget, capabilities, and so on associated with exemplary data consumer106.

Regarding Underwriting/Onboarding 210, user information about user orcustomer (e.g., user 102) solicited, provided, collected, used,distributed, and so on, as well as costs and efficiencies therewith canfacilitate efficiently determining available product mix, reserverequirements, product competitiveness, and so on associated withexemplary data consumer 106.

In terms of Account Management 212, user information about user orcustomer (e.g., user 102) solicited, provided, collected, used,distributed, and so on, as well as costs and efficiencies therewith canfacilitate efficiently performing comprehensive capital analysis andreview, portfolio bundling, determining marketing budget, improvingcustomer experience, determining depth of wallet, and so on associatedwith exemplary data consumer 106.

In terms of Debt Management 214, user information about user or customer(e.g., user 102) solicited, provided, collected, used, distributed, andso on, as well as costs and efficiencies therewith can facilitateefficiently determining internal staff budget, recovery rates,capabilities, and so on associated with exemplary data consumer 106. Ascan be seen from the analysis of the activities or events of blockdiagram 200 associated with user or customer (e.g., user 102), userinformation about user or customer (e.g., user 102) solicited, provided,collected, used, distributed, and so on, can have costs and efficienciesassociated, and can have a direct impact on the business operations.

Moreover, it can be understood that once user information about user orcustomer (e.g., user 102) is out of the possession of user or customer(e.g., user 102) and within the business structure and processes ofexemplary data consumer 106, it can be complicated or virtuallyimpossible for user or customer (e.g., user 102) to detect or correcterrors with the business structure and processes of exemplary dataconsumer 106. While interests of user or customer (e.g., user 102) andexemplary data consumer 106 may be aligned as to the veracity andcompleteness of the user information about user or customer (e.g., user102), there may be no communication process between exemplary dataconsumer 106 and user or customer (e.g., user 102) established forproactive detection and correction. The default may be only errorcorrection on detection, and detection only in the event of activebusiness activity between exemplary data consumer 106 and user orcustomer (e.g., user 102). In other words, barring a profitable businessopportunity, there is no motive for either of exemplary data consumer106 or user or customer (e.g., user 102) to proactively control andcorrect user information about user or customer (e.g., user 102),notwithstanding the lack of an ability for user or customer (e.g., user102) to control user information about user or customer (e.g., user 102)within the business structure and processes of exemplary data consumer106.

As a result, such situations give rise to the problems of theproliferation of relatively cheap and/or easy access to user informationabout user or customer (e.g., user 102), with the business processes andstructure historically developed, with attendant costs associated withrisk mitigation, to focus primarily on the verification of the cheapand/or easy access to user information. Such costs include frauddetection and prevention, information security, underwriting, accountmonitoring and management, and so on, as described regarding FIG. 2.Accordingly, various embodiments of the disclosed subject matterfacilitate creating and using a data safe or user data safe 112 for userinformation or user personal information, as further described herein.Non-limiting embodiments of data safe or user data safe 112 as describedherein can facilitate enhanced user 102 control over the provision,collection, use, distribution, and so on, of user information about user102 and can facilitate providing further benefits from achievingefficiencies in the proper or authorized provision, collection, use,distribution, and so on, of user information about user 102.

FIG. 3 illustrates an exemplary block diagram 300 showing furthernon-limiting aspects of embodiments of the disclosed subject matter. Asdescribed, various embodiments of data safe or user data safe 112 asdescribed herein can facilitate enhanced user 102 control over theprovision, collection, use, distribution, and so on, of user informationabout user 102 and can facilitate providing further benefits fromachieving efficiencies in the proper or authorized provision,collection, use, distribution, and so on, of user information about user102. For example, exemplary data safe or user data safe 112 canfacilitate enhanced user 102 control over the provision, collection,use, distribution, and so on, of user information about user 102comprising or associated with one or more of personal identificationinformation 302, income information 304, employment information 306,investment information 308, credit card information 310, medical historyinformation 312, account/login information 314, payment information 316,etc., without limitation.

For example, FIG. 4 illustrates non-limiting examples of userinformation about a user that can be employed in the provision,collection, use, distribution, and so on, of user information about theuser, in accordance with various embodiments of an exemplary data safeor user data safe 112 as described herein.

Exemplary non-limiting examples of personal identification information302 can comprise or be associated with one or more of name, address,Social Security number (SSN), date of birth, phone number, emailaddress, emergency contact, emergency phone number, an electronicsignature, a uniform resource identifier (URI) to identity file ofverification entity (e.g., verifying entity 110), and so on, withoutlimitation, in non-limiting aspects.

In further non-limiting aspects, exemplary non-limiting examples ofincome information 304 can comprise or be associated with one or more ofa paystub URI or uniform resource locator (URL), a username, password, apayroll provider, and so on, without limitation.

Exemplary non-limiting examples of employment information 306 cancomprise or be associated with one or more of current employer,employment start date, previous or prior employer, start and end dates,and so on, without limitation, in still other non-limiting aspects.

In addition, exemplary non-limiting examples of investment information308 can comprise or be associated with one or more of 401(k) URL,brokerage1 URL, brokerage2 URL, banking institution1, username(s),password(s), account number(a), and so on, without limitation, innon-limiting aspects.

In still other non-limiting embodiments, exemplary non-limiting examplesof credit card information 310 can comprise or be associated with one ormore of card or account number(s), expiration date(s), card verificationvalue(s) (CVV), and so on, without limitation, in non-limiting aspects,as illustrated in FIG. 4.

Exemplary non-limiting examples of medical history information 312 cancomprise or be associated with one or more of insurance provider, policynumber, family disease history, current prescriptions, past treatmentsand events, primary care physician, service provider, and so on, withoutlimitation, in still further non-limiting aspects.

More generally, exemplary non-limiting examples of account/logininformation 314 can comprise or be associated with one or more of siteURL(s), same username(s), site password(s) and so on, withoutlimitation, in further non-limiting aspects.

In addition, exemplary non-limiting examples of payment information 316can comprise or be associated with one or more of a payment entityusername, a payment entity password, a PayPal username, a PayPalpassword, a mobile payment service, username, a mobile payment servicepassword, a block chain username, a block chain password, a meta-maskusername, a meta-mask, password, and so on, without limitation, innon-limiting aspects.

As described, various embodiments of data safe or user data safe 112 asdescribed herein can facilitate enhanced user 102 control over theprovision, collection, use, distribution, and so on, of user informationabout user 102, as well as facilitate the validation, verification,authentication, and proper protection and control of such userinformation about user 102, to ensure smooth, efficient, andcost-effective business processes. Accordingly, various embodiments asdescribed herein can provide further benefits from achievingefficiencies in the proper or authorized provision, collection, use,distribution, and so on, of user information about user 102.

As used herein, user information about user 102 can be referred to aspersonal information, without limitation, regardless of whether anexemplary user 102 comprises an individual human person, properlyauthorized and authenticated to use data safe or user data safe 112,whether exemplary user 102 comprises any of a number of real orintangible entities about which user information is desired by one ormore data consumer(s) 106, or whether one or more computer-executablecomponents acting on behalf of exemplary user 102.

As depicted in FIGS. 3 and 4, personal information can comprise personalidentification information (PII), and/or other personal information(OPI), according to various non-limiting aspects. Exemplary PII orpersonal identification information 302, as used herein, can comprise orbe associated with information or combinations of information thatresolve to a unique user 102. Thus, in a non-limiting aspect, userinformation comprising PII or personal identification information 302can be determined to be PII or personal identification information 302,based in part on such information or combinations of informationresolving to a unique user 102 beyond a predetermined thresholdconfidence level. In a non-limiting aspect, one combination ofinformation, such as name and mailing address ZIP Code may resolve touser 102 with a first level of confidence, which may meet or exceed afirst predetermined threshold confidence level. In another non-limitingaspect, another combination of information, such as name, currentaddress, and date of birth may resolve to user 102 with a second levelof confidence, which may meet or exceed a second predetermined thresholdconfidence level. In still another non-limiting aspect, anothercombination of information, such as name and SSN may resolve to user 102with a third level of confidence, which may meet or exceed a thirdpredetermined threshold confidence level.

In still further non-limiting examples, it can be understood thatexemplary PII or personal identification information 302 can comprise orbe associated with further categories of personal information, such asbut not limited to, biometric information associated with user 102,including, but not limited to fingerprint data, facial recognition,data, retinal scan data, DNA information, and so on, one or moreauthentication factors in a multifactor authentication process,cryptographic tokens, digital certificates, radiofrequencyidentification (RFID) and/or near field communication (NFC) informationor packets, and so on, whether self-verified such as via entry ofpersonal information on a digital form, or whether one or more verifyingentities 110 are employed to enhance the confidence in the subjectpersonal information. Accordingly, while particular non-limitingexamples of personal identification information 302 are described above,for the purposes of illustration, it can be understood that PII orpersonal identification information 302, is not limited by the scope ofembodiments described herein.

As described, personal information can comprise personal identificationinformation such as personal identification information 302, and/orother personal information (OPI), according to various non-limitingaspects. As contrasted with PII or personal identification information302, OPI can comprise information or combinations of information that donot resolve to a unique user 102 beyond the predetermined thresholdconfidence level, for example, without more. A non-limiting examplemight be a doctor's record or an account balance, that withoutadditional information such as a patient ID, account number, entity,etc., cannot be used to resolve whether the information comprising OPIrelates to or is associated with unique user 102 beyond thepredetermined threshold confidence level.

As further described herein, for example, regarding FIGS. 5-14, 15-19,etc., various embodiments of data safe or user data safe 112 canfacilitate enhanced user 102 control over the provision, collection,use, distribution, and so on, of user information about user 102 as wellas facilitate the validation, verification, authentication, and properprotection and control of such user information about user 102, toensure smooth, efficient, and cost-effective business processes, byemploying further non-limiting examples of information associated withuser 102 (e.g., categories of use, supplemental information, otherinformation, other authorization information, etc.).

FIG. 5 illustrates an exemplary flow diagram of methods 500 directed tocreation of user information or data block chains according non-limitingaspects of embodiments of the disclosed subject matter.

As a non-limiting example, exemplary methods 500 can comprise, at 502,storing, by a device comprising a processor (e.g., device or system2000, 2200, 2300, portions thereof, etc.) personal informationassociated with a user in a distributed file system (DFS), as furtherdescribed herein, regarding FIGS. 6-14, 15-19, and 20-26, for example.For instance, in a non-limiting aspect of exemplary methods 500, thestoring the personal information can comprise encrypting, via the device(e.g., device or system 2000, 2200, 2300, portions thereof, etc.), thepersonal information with supplemental information to facilitatecreation of one or more block chain(s) of the plurality of block chains,determination an applicability status of the request for authorization,and so on. In a further non-limiting aspect of exemplary methods 500,the storing the personal information in DFS can comprise storing, viathe device (e.g., device or system 2000, 2200, 2300, portions thereof,etc.), the personal information in inter-planetary file system (IPFS).

In another non-limiting aspect of exemplary methods 500, the encryptingthe personal information with supplemental information can compriseencrypting, via the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), a plurality of a cryptographic hash of a priorblock of personal information in the one or more block chain(s), a linkto the prior block of personal information in the one or more blockchain(s) stored in the DFS, a verifying entity associated with thepersonal information, a digital signature associated with the verifyingentity, information associated with an encryption key or decryption key,or other authorization information associated with the set of theplurality of block chains, as further described herein, regarding FIGS.6-14, 15-19, and 20-26, for example. For example, in a furthernon-limiting aspect of exemplary methods 500, the encrypting the otherauthorization information associated with the set of the plurality ofblock chains can comprise encrypting, via the device (e.g., device orsystem 2000, 2200, 2300, portions thereof, etc.), one or more term ofuse determined by the user. As a further non-limiting example accordingto further aspects of exemplary methods 500, the encrypting the link tothe prior block of personal information in the one or more blockchain(s) can comprise encrypting, via the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), an encrypted link to theprior block of personal information in the one or more block chain(s).

In another non-limiting example, exemplary methods 500 can comprise, at504, creating, by the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), a plurality of block chains of personalinformation, based on a determined category of use of each of theplurality of block chains, as further described herein, regarding FIGS.6-14, 15-19, and 20-26, for example.

As a non-limiting example, exemplary methods 500 can further comprisecreating the plurality of block chains of personal information which cancomprise determining, via the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), whether the personal information ispersonal identification information or other personal information,wherein the personal identification information is defined asinformation or combinations of information that resolve to a uniqueuser, meeting or exceeding a predetermined threshold confidence level,and wherein the other personal information is defined as otherinformation or combinations of other information that does not resolveto the unique user, by failing to meet or exceed the predeterminedthreshold confidence level, and creating the plurality of block chainsbased on at least the personal identification information.

In addition, exemplary methods 500 can further comprise, at 506,receiving, via the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), the request for authorization, as furtherdescribed herein, regarding FIGS. 6-14, 15-19, and 20-26, for example.

In yet another non-limiting example, exemplary methods 500 can comprise,at 508, determining, via the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), from the request for authorization thedetermined category of use, as further described herein, regarding FIGS.6-14, 15-19, and 20-26, for example.

In still another non-limiting example, exemplary methods 500 cancomprise, at 510, determining, via the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), whether one or moreresponsive block chain exists that is responsive to the determinedcategory of use and the request for authorization in the set of theplurality of block chains, as further described herein, regarding FIGS.6-14, 15-19, and 20-26, for example.

In further non-limiting examples, exemplary methods 500 can comprise, at512, creating, via the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), the one or more responsive block chain if theone or more responsive block chain does not exist, as further describedherein, regarding FIGS. 6-14, 15-19, and 20-26, for example.

As a non-limiting example, exemplary methods 500 can comprise, at 514,transmitting an authorization, by the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), to access a set of theplurality of block chains based on the determined category of useassociated with a request for authorization, as further describedherein, regarding FIGS. 6-14, 15-19, and 20-26, for example.

In another non-limiting example, exemplary methods 500 can comprise, at516 transmitting the authorization comprising transmitting, via thedevice (e.g., device or system 2000, 2200, 2300, portions thereof,etc.), one or more cryptographic hash associated with a last block ofthe one or more responsive block chain and a link to the last block ofthe one or more responsive block chain stored in the DFS, as furtherdescribed herein, regarding FIGS. 6-14, 15-19, and 20-26, for example.

For instance, in another non-limiting aspect of exemplary methods 500,the transmitting the one or more cryptographic hash associated with thelast block of the one or more responsive block chain and the link to thelast block of the one or more responsive block chain stored in the DFScan comprise encrypting, via the device (e.g., device or system 2000,2200, 2300, portions thereof, etc.), the one or more cryptographic hashassociated with the last block of the one or more responsive block chainand the link to the last block of the one or more responsive block chainwith a requester encryption key.

In another non-limiting example, exemplary methods 500 can comprisedetermining, via the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), the one or more term of use, comprising one ormore of an expiration term for one or more of the authorization or thepersonal information, a validity term associated with the personalinformation, one or more of a payee or a requested fee associated withthe one or more of the authorization or the personal information, one ormore of a transmission limit or a storage limit associated with the oneor more of the authorization or the personal information, or arestriction associated with the one or more of the authorization or thepersonal information on a third party, as further described herein,regarding FIGS. 6-14, 15-19, and 20-26, for example.

FIGS. 6-14 illustrates a flow diagram of non-limiting aspects of anexemplary process for creation of user information or data block chainsaccording non-limiting aspects of embodiments of the disclosed subjectmatter.

FIG. 6 illustrates a flow diagram of non-limiting aspects of exemplaryprocesses 600 for creation of user information or data block chainsand/or use thereof according non-limiting aspects of embodiments of thedisclosed subject matter.

For instance, FIG. 6 depicts exemplary processes 600 for creation ofuser information or data block chains and/or use thereof, beginning at602. As further described herein regarding FIGS. 5 and 8-10, exemplaryprocesses 600 can comprise, at 604, storing, by a device comprising aprocessor (e.g., device or system 2000, 2200, 2300, portions thereof,etc.) personal information (PI) associated with a user in a distributedfile system (DFS), as further described herein. In another non-limitingaspect, at 608, exemplary processes 600 can comprise creating, by thedevice (e.g., device or system 2000, 2200, 2300, portions thereof,etc.), a plurality of block chains of personal information, based on adetermined category of use of each of the plurality of block chains, asfurther described herein, regarding FIGS. 5 and 8-10. As shown in FIG.6, storing one or more blocks of encrypted personal information (PI) indistributed file system (DFS) and creating a set of block chains of aset of PI based on one or more categories of use (CI) and one or morestored blocks of encrypted PI as further described regarding off-pagereference A, 606, in FIGS. 8-10.

In a further non-limiting aspect, exemplary processes 600 can comprise,at 610, transmitting an authorization, by the device (e.g., device orsystem 2000, 2200, 2300, portions thereof, etc.), to access a set of theplurality of block chains based on the determined category of useassociated with a request for authorization, as further describedherein, regarding FIGS. 5 and 11-12. As a non-limiting example, toauthorize access to one or more PI block chains based on a desiredcategory of use (CI) at 610, exemplary processes 600 can comprise, at612, receiving, via the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), the request for authorization, as furtherdescribed herein, regarding FIGS. 5 and 11-12, which can comprise arequest for personal information (PI), one or more categories of use(CI) of the requested PI, and/or information from which it can bedetermined or resolved the one or more categories of use (CI) of therequested PI. As a further non-limiting example, to authorize access toone or more PI block chains based on a desired category of use (CI) at610, exemplary processes 600 can comprise, at 614, determining, via thedevice (e.g., device or system 2000, 2200, 2300, portions thereof,etc.), from the request for authorization the determined category of use(CI), as further described herein, regarding FIGS. 5 and 11-12.

In yet another non-limiting example, to authorize access to one or morePI block chains based on a desired category of use (CI) at 610,exemplary processes 600 can comprise, at 616, determining, via thedevice (e.g., device or system 2000, 2200, 2300, portions thereof,etc.), whether one or more responsive block chain exists that isresponsive to the determined category of use and the request forauthorization in the set of the plurality of block chains, as furtherdescribed herein, regarding FIGS. 5, 7, and 11. Thus, if it isdetermined that the PI block chain does not exist (e.g., whether one ormore responsive block chains exist, etc.), at 618, the exemplaryprocesses 600 can facilitate, at 608, the storing of one or more blocksof encrypted personal information (PI) in distributed file system (DFS)and creating a set of block chains of a set of PI based on one or morecategories of use (CI) and one or more stored blocks of encrypted PI asfurther described above regarding off-page reference A, 606, in FIGS.8-10. Alternatively, if it is determined that the PI block chain exists(e.g., whether one or more responsive block chain exists, etc.), at 618,the exemplary processes 600 can proceed through off-page reference B,620, as further described herein, regarding FIGS. 7 and 11-12.

For example, FIG. 7 illustrates a flow diagram of non-limiting aspectsof exemplary processes 700 that facilitates authorizing access to one ormore PI block chains based on a desired category of use (CI) accordingnon-limiting aspects of embodiments of the disclosed subject matter.

As a non-limiting example, exemplary processes 700 can comprise, at 702,determining s last subsequent block of an existing block chain based onone or more categories of use (CI). For instance, as described herein, ablock chain typically comprises a growing list of records, calledblocks, which are linked using cryptography, where each block cancomprise a cryptographic hash of the previous block, a timestamp, and/orother data such as transaction data in conventional use. Thus, a blockchain block as described herein can be referred to as a root block,which can be understood to be a first block in the block chain or agenesis block, which may be first in time, but need not be, according tovarious non-limiting aspects, a last block, which can be understood tobe a last block in the block chain or a current block, which may be lastin time, but need not be, according to further non-limiting aspects, anda subsequent block, which would be subsequent to or follow a root blockin a block chain, and for which any number of subsequent blocks mayfollow the root block. By way of example of an exemplary three block,block chain, the “last” block, “last subsequent” block, or current blockin the block chain would follow a subsequent block that is immediatelyprior in the block chain, and the subsequent block would follow the rootblock or genesis block, for example, as further described hereinregarding FIGS. 8 and 11-12.

For instance, upon receiving a request for authorization to access a setof the plurality of block chains and determining that a responsive blockchain exists that is responsive to the determined one or more categoriesof use (CI) and the request for authorization in the set of theplurality of block chains, at 618, exemplary processes 700 can comprise,at 702, determining a last subsequent block of an existing block chainbased on one or more categories of use (CI), for example, as furtherdescribed herein regarding FIGS. 9 and 11-12.

As a further non-limiting example, exemplary processes 700 can comprise,at 704, determining a hash (e.g., a cryptographic hash, etc.) of thelast subsequent block and a link returned, for example, as furtherdescribed herein regarding FIGS. 8-10. For example, as further describedherein regarding FIGS. 8-10 and 12, a block of personal information canbe encrypted and stored in DFS. In a non-limiting aspect, a hash or acryptographic hash can be computed for the encrypted block of personalinformation, which in further non-limiting aspects, can be, but need notbe, used as a link or uniform resource identifier (URI) to facilitateunambiguously identifying, locating, and/or sharing the encrypted blockof personal information, according to various non-limiting embodimentsdescribed herein, for example, regarding FIGS. FIGS. 8-10 and 12. Thus,at 704, exemplary processes 700 can comprise determining a hash (e.g., acryptographic hash, etc.) of the last subsequent block of PI and a linkreturned (e.g., as a result of storage in the DFS), for example, asfurther described herein regarding FIGS. 8-10, from off-page referenceC, 706, from FIG. 9.

In another non-limiting example, exemplary processes 700 can comprise,at 708, determining other authorization information (OAI). For instance,according to various non-limiting embodiments described herein, contentsof blocks in a block chain can comprise various categories ofinformation, including, but not limited to, personal information (PI),which can include personal identification information (PII) and otherpersonal information (OPI), as described above, supplemental information(SI), which can comprise other authorization information (OAI), andother information, for example, as further described herein, regardingFIGS. 8-10 and 12. As used herein, other authorization information (OAI)can comprise or be associated with restrictions specified by a user, ora system or a device on behalf of the user, regarding the provision,collection, use, storage, distribution, and so on, of user informationabout the user (e.g., personal information (PI)), as well as relating tothe validation, verification, authentication, and/or proper protectionand control user information about the user (e.g., personal information(PI)). Accordingly, non-limiting examples of other authorizationinformation (OAI) can include, but are not limited to, terms of use,information expiration term (e.g., a time-based limit on validity),information validity term (e.g., other context-based limit on validity),fee-based restrictions or limitations and/or payee information,including but not limited to, payment method, transmission and/orstorage limits and/or restrictions, limits and/or restrictions onthird-party access, whether generalized or specific, and so on, links tosuch OAI, whether contained in the block or response, as the case maybe, or incorporated by reference to a linked resource, etc., accordingto various non-limiting aspects. Accordingly, exemplary processes 700can comprise, at 708, determining other authorization information (OAI),if any, to include in the block of PI to be stored in DFS or a responseto be sent in reply to a request for authorization to access PI, as thecase may be, for example, as further described herein, regarding FIGS.8-10 and 12.

As a further non-limiting example, exemplary processes 700 can comprise,at 710, encrypting a hash (e.g., a cryptographic hash, etc.) of the lastsubsequent block of PI and a link returned (e.g., as a result of storagein the DFS), as determined at 704, for example, as further describedherein regarding FIGS. 9 and 11-12. For instance, as further describedherein, various non-limiting embodiments can comprise transmitting theauthorization comprising transmitting, via the device (e.g., device orsystem 2000, 2200, 2300, portions thereof, etc.), one or morecryptographic hash associated with a last block of the one or moreresponsive block chain and a link to the last block of the one or moreresponsive block chain stored in the DFS, as further described herein.Thus, a hash (e.g., a cryptographic hash, etc.) of the last subsequentblock of PI and a link returned (e.g., as a result of storage in theDFS), as determined at 704, can be encrypted, at 710. In yet anothernon-limiting example, exemplary processes 700 can comprise, at 712,sending encrypted response to requestor.

As further described herein, various encryption operations can beemployed to facilitate the provision, collection, use, storage,distribution, and so on, of user information about the user (e.g.,personal information (PI)), as well as relating to the validation,verification, authentication, and/or proper protection and control userinformation about the user (e.g., personal information (PI)), accordingto non-limiting aspects as described herein. As a non-limiting example,in FIG. 7, at 710, exemplary processes 700 can comprise, encrypting ahash (e.g., a cryptographic hash, etc.) of the last subsequent block ofPI and a link returned (e.g., as a result of storage in the DFS), asdetermined at 704, for example, as further described herein regardingFIGS. 9 and 11-12. Such encryption may be, but need not be, by way ofpublic-key cryptography. As non-limiting examples, at 710, exemplaryprocesses 700 can comprise, encrypting a hash (e.g., a cryptographichash, etc.) of the last subsequent block of PI and a link returned(e.g., as a result of storage in the DFS), as determined at 704, using auser's private key, which information would be decrypted using user'spublic key, using a requestor's public key, for example, which would besent in an exemplary request for access to one or more PI block chains,as further described herein, regarding FIGS. 11-12, for example, and/orusing another agreed-upon encryption protocol, without limitation.

Thus, having sent encrypted response to the requestor, at 712, exemplaryprocesses 700 can terminated at 714.

As further described above regarding FIG. 6, FIG. 8 illustrates a flowdiagram of non-limiting aspects of exemplary processes 800 for creationof user information or data block chains, according non-limiting aspectsof embodiments of the disclosed subject matter. Accordingly, FIG. 6proceeds from storing one or more blocks of encrypted personalinformation (PI) in distributed file system (DFS) and creating a set ofblock chains of a set of PI based on one or more categories of use (CI)and one or more stored blocks of encrypted PI to off-page reference A,606, in FIG. 8.

Thus, at 802, exemplary processes 800 can comprise determining whetherpersonal information (PI) is personal identification information (PII)or other personal information (OPI). As further described herein,regarding FIGS. 3-4, for example, exemplary PII or personalidentification information 302, as used herein, can comprise or beassociated with information or combinations of information that resolveto a unique user 102. Thus, in a non-limiting aspect, user informationcomprising PII or personal identification information 302 can bedetermined to be PII or personal identification information 302, basedin part on such information or combinations of information resolving toa unique user 102 beyond a predetermined threshold confidence level,whereas OPI can comprise information or combinations of information thatdo not resolve to a unique user 102 beyond the predetermined thresholdconfidence level, for example, without more.

In a further non-limiting example, having determined that the personalinformation (PI) to be stored in DFS is personal identificationinformation (PII), at 804, exemplary processes 800 can comprise creatinga root block of PI to store in DFS, at 806. Otherwise, having determinedthat the personal information (PI) is other personal information (OPI),at 808, exemplary processes 800 can comprise creating a subsequent blockof PI to store in DFS, at 810. As described above, an exemplarysubsequent block would follow an exemplary root block to construct ablock chain of personal information (PI) to be stored DFS. As depictedin FIG. 8, exemplary embodiments as described herein can comprisecreating one or more block chains of user information or data about auser 102 or personal information (PI), wherein the root block comprisespersonal identification information (PII). However, in furthernon-limiting aspects, further exemplary embodiments can comprisecreating one or more block chains of user information or data about auser 102 or personal information (PI), wherein the root block does notnecessarily comprise personal identification information (PII). As anon-limiting example, in last or last subsequent block, and/or anysubsequent block in the block chain as described herein can comprisepersonal identification information (PII). In other non-limitingexamples, personal identification information (PII) can be spread acrossa number of blocks of a block chain, such that combinations ofinformation spread across the number of blocks can resolve to a uniqueuser 102 (e.g., beyond the predetermined threshold). In still anothernon-limiting example, various embodiments can facilitate creating one ormore block chains of user information or data about a user 102 orpersonal information (PI), wherein none of the blocks in a block chaincomprise personal identification information (PII).

Nevertheless, having created a block of personal information (PI) to bestored in DFS, exemplary processes 800 can comprise determining one ormore categories of use of the PI, at 812. As can be understood, somepieces of personal information (PI), can be used for useful for multiplecategories of use. As a non-limiting example, personal identificationinformation (PII), can be useful almost universally (e.g., employment,investment, lending, service provision, insurer assessment, etc.),whereas other pieces of personal information (PI) would be useful onlyin the most limited of circumstances (e.g., employment interviewavailability dates, desired salary, last medical exam, credit cardpurchase on a particular date, etc.). In addition, a user 102 may desireto restrict the purposes for which user information or data about a user102 or personal information (PI) stored in DFS is available for use. Asa non-limiting example, user 102 may store in DFS a block of personalinformation (PI) relating to employment history, for the purpose ofinterviewing with prospective employers. However, as a furthernon-limiting example, user 102 may desire to restrict use of thatpersonal information (PI), for example, for other purposes, such as,lending, and so on. Accordingly, exemplary processes 800 can comprise,at 812, determining one or more categories of use of the PI to be storedin the block of personal information (PI) in DFS, for example, asfurther described herein, regarding FIGS. 9-10.

In addition, exemplary processes 800 can comprise, at 812, determiningsupplemental information (SI) to be stored with personal information(PI) in a block of a block chain in DFS, for example, as furtherdescribed herein, regarding FIGS. 9-10. As a non-limiting example, inaddition to other authorization information (OAI), for example, asdescribed above regarding FIG. 7, supplemental information (SI) cancomprise or be associated with meta information or supplementalinformation such as alternate or additional names, addresses, etc.,contact information or referral information, account passwords orlimited-time use access codes, authorized or associated side blockchains, and so on, in addition to that information as further describedherein, regarding FIGS. 9-10. As a non-limiting example, variousembodiments as described herein can comprise supplemental information(SI) (e.g., SI (PI BLOCK (n))) comprising other authorizationinformation (OAI), as described above, a hash (e.g., a cryptographichash) of the prior block of personal information (PI) stored in DFS(e.g., HASH OF PI BLOCK (n−1)), a URI or link of the prior block ofpersonal information (PI) stored in DFS (e.g., URI/LINK OF PI BLOCK(n−1)), a verifying entity associated with personal information (PI) inor associated with the block (e.g., VERIFYING ENTITY), a verifyingentity digital signature associated with personal information (PI) in orassociated with the block (e.g., VERIFYING ENTITY DIGITAL SIGNATURE),encryption/decryption keys, if any, to facilitate decryption of personalinformation (PI) stored in one or more blocks of the one or more blockchains of personal information (PI) stored in DFS (e.g.,ENCRYPTION/DECRYPTION KEY(S)), and so on, without limitation, forexample, as further described herein, regarding FIGS. 9-13. As anon-limiting example, supplemental information (SI) comprising one ormore encryption/decryption keys, if any, to facilitate decryption ofpersonal information (PI) stored in one or more blocks of the one ormore block chains of personal information (PI) stored in DFS (e.g.,ENCRYPTION/DECRYPTION KEY(S)) can be employed to facilitate decryptingone or more blocks of personal information (PI) stored in DFS, accordingto a predetermined encryption protocol or agreement between a user 102and a requestor, for example, comprising a data consumer 106, and/or viaone or more devices or systems acting on their behalf, in furthernon-limiting aspects.

Exemplary processes 800 can continue via off-page reference D, 816. Forinstance, FIG. 9 illustrates a flow diagram of further non-limitingaspects of exemplary processes 900 for creation of user information ordata block chains, according non-limiting aspects of embodiments of thedisclosed subject matter. Accordingly, exemplary processes 900 cancomprise, at 902, creating or continuing a block chain of personalinformation (PI) to be stored in DFS. As a non-limiting example, if itis determined that it is desired to create or continue a block chain ofpersonal information (PI) based on one or more categories of use (CI) tobe stored in DFS, at 904, it can be determined at 906, whether or not anexisting block chain, at 906, in various non-limiting embodiments.

If it is determined that an existing block chain does not exist (e.g., aroot block is to be created at 806, etc.), at 906, then, at 908, a URIor link to the root block and a hash (e.g., a cryptographic hash) of theroot block can be included in supplemental information (SI), at 908. Ifit is determined that an existing block chain does exist (e.g., asubsequent block is to be created at 810, etc.), at 906, then, at 910, aURI or link to the last subsequent block and a hash (e.g., acryptographic hash) of the last subsequent block can be included insupplemental information (SI), at 910. In further non-limitingembodiments, the URI or link to the root block or the last subsequentblock, as the case may be, may be further encrypted to facilitatefurther compartmentalization, protection, and control over unauthorizedaccess and dissemination of personal information (PI) stored in the oneor more block chain stored in DFS, for example, according to apredetermined encryption protocol or agreement between a user 102 and arequestor, for example, comprising a data consumer 106, and/or via oneor more devices or systems acting on their behalf, in furthernon-limiting aspects.

In further non-limiting examples, at 912, exemplary processes 900 cancomprise addending any supplemental information (SI) to personalinformation (PI) to be stored in the block of the block chain stored inDFS, prior to encrypting the personal information (PI) and thesupplemental information (SI) at 914, and prior to storing the encryptedpersonal information (PI) and the supplemental information (SI) in DFSat 916.

Further non-limiting examples of exemplary processes 900 can comprise,at 918, creating a URI or link to the encrypted personal information(PI) and the supplemental information (SI) stored in DFS. In anon-limiting aspect, creating a URI or link to the encrypted personalinformation (PI) and the supplemental information (SI) stored in DFS cancomprise employing a hash (e.g., a cryptographic hash) of the encryptedpersonal information (PI) and the supplemental information (SI) storedin DFS as the URI or link. For instance, various embodiments describedherein can employ exemplary hash functions that can be used to map dataof arbitrary size (e.g., personal information (PI), supplementalinformation (SI), combinations thereof, etc.) to data of a fixed size,wherein values returned by an exemplary hash function can be referred toherein as hashes, such as cryptographic hashes, the employment of which,according to various the embodiments described herein, can facilitateassuring integrity of stored and/or transmitted data (e.g., personalinformation (PI), supplemental information (SI), combinations thereof,stored in DFS, etc.). Accordingly, in another non-limiting example,exemplary processes 900 can comprise, at 920, taking the hash (e.g., acryptographic hash) of the encrypted personal information (PI) and thesupplemental information (SI) stored in DFS and the URI or link, if any,and, at 922, storing the hash (e.g., a cryptographic hash) of theencrypted personal information (PI) and the supplemental information(SI) stored in DFS and the URI or link, if any, for further use, such asby transmitting or determining the hash (e.g., a cryptographic hash) ofthe encrypted personal information (PI) and the supplemental information(SI) stored in DFS and the URI or link, via off-page reference C, 706,in exemplary processes 700, for example.

As described above regarding FIGS. 6 and 8, for example, variousembodiments as described herein can facilitate creation of userinformation or data (e.g., personal information (PI)) block chains.Accordingly, FIG. 10 illustrates an exemplary embodiment of a userinformation or data (e.g., personal information (PI)) block chain thatcan be stored in DFS according to various non-limiting embodiments. Asfurther described herein, FIG. 10 can comprise a last or last subsequentblock 1002 (e.g., PI BLOCK(n)[PII+OPI+SI]), and immediately priorsubsequent block 1004 (e.g., PI BLOCK(n−1)[PII+OPI+SI]), and a rootblock 1006 (e.g., PI BLOCK(0)[PII+OPI+SI]). According to variousnon-limiting embodiments, an exemplary block chain of personalinformation (PI) stored in DFS can comprise less than three blocks, asillustrated in FIG. 10. In further non-limiting embodiments, anexemplary block chain of personal information (PI) stored in DFS canalso comprise more than three blocks, as illustrated in FIG. 10. In afurther non-limiting aspect, while FIG. 10 depicts last or lastsubsequent block 1002, immediately prior subsequent block 1004, and rootblock 1006 with personal identification information (PII), as furtherdescribed herein, in the headings and the body of the blocks of theexemplary block diagram, this should be understood to illustrate thecapability to store personal identification information (PII) in last orlast subsequent block 1002, immediately prior subsequent block 1004, androot block 1006, and not as a requirement that each of last or lastsubsequent block 1002, immediately prior subsequent block 1004, and rootblock 1006, store such personal identification information (PII), asfurther described herein. Thus, the exemplary block diagram of FIG. 10should be understood such that each of each of last or last subsequentblock 1002, immediately prior subsequent block 1004, and root block 1006can facilitate storage of some, none, all, whether determining whetherthe personal information (PI) is personal identification information(PII), as further described herein, in combination with personalinformation (PI) in other blocks, or otherwise.

Thus, FIG. 10 depicts the capability of blocks of personal information(PI), according to various non-limiting aspects as described herein, tostore one or more of personal identification information (PII), atimestamp, one or more categories of use of the personal information(PI) comprised in or associated with the one or more blocks, otherpersonal information (OPI), supplemental information (SI), otherauthorization information {OAI}, and so on, without limitation, forexample, as further described herein, regarding FIG. 1-9. FIG. 10,further depicts the capability of blocks of personal information (PI),according to further non-limiting aspects as described herein, to storeother information, for example, not described by the above categories ofinformation. As a non-limiting example, other information can compriseor be associated with and/or facilitate further uses or restrictionsassociated with the one or more blocks and/or block chains of personalinformation (PI) stored in DFS, as further described herein. As afurther non-limiting example, other information can comprise alimitation on acceptance of an offer, counter offer, terms, and so on,without limitation, for example, as further described herein, regardingFIGS. 15-19.

FIG. 10 further depicts the ability to facilitate creation of blockchains of PI stored in DFS, wherein exemplary last or last subsequentblock 1002 (e.g., PI BLOCK(n)[PII+OPI+SI]) stores a HASH of PI BLOCK(n−1), to facilitate verifying the integrity of the data stored inimmediately prior subsequent block 1004 (e.g., PIBLOCK(n−1)[PII+OPI+SI]) and/or the URI/LINK of PI BLOCK (n−1), to locatesuch immediately prior subsequent block 1004 (e.g., PIBLOCK(n−1)[PII+OPI+SI]) in DFS. It can be understood that the blockchain can be located by similar mechanism (e.g., locate, decrypt,retrieve URI and HASH of prior block, etc.) through to root block 1006(e.g., PI BLOCK(0)[PII+OPI+SI]), according to the various non-limitingaspects described herein regarding FIGS. 6-9, etc.

FIG. 11 provides a non-limiting block diagram 1100 illustrating anexemplary request and response interaction, for example, between a user(e.g., a user 102) and a requestor (e.g., a data consumer 106), asfurther described herein. As can be understood, such requests andresponses, as further described herein can be made by one or moredevices or systems acting respectively on behalf of user 102 and dataconsumer 106, for example, as further described herein regarding FIGS.15 to 20. As further described above regarding FIG. 6, to authorizeaccess to one or more PI block chains based on a desired category of use(CI) at 610, exemplary processes 600 can comprise, at 612, receiving,via the device (e.g., device or system 2000, 2200, 2300, portionsthereof, etc.), the request for authorization, as further describedherein, regarding FIGS. 5 and 11-12, which can comprise a request forpersonal information (PI), one or more categories of use (CI) of therequested PI, and/or information from which it can be determined orresolved the one or more categories of use (CI) of the requested PI.Accordingly, as further described herein, a requestor (e.g., a dataconsumer 106) and/or one or more devices or systems acting on therequestor's behalf can send a request to authorize access to one or morepersonal information (PI) block chains stored in DFS, based on a desiredcategory of use, at 1102, as depicted in FIG. 11. As a non-limitingexample, a lender (or one or more devices or systems acting respectivelyon behalf of the lender) could send a request to authorize access to oneor more personal information (PI) block chains stored in DFS, based on aprospective offer for financing, etc.

FIG. 11 further depicts an exemplary request 1104, according to variousnon-limiting aspects. As described above regarding FIG. 10, FIG. 11depicts the capability of exemplary requests, such as depicted withrespect to exemplary request 1104, according to various non-limitingaspects as described herein, to comprise or be associated with one ormore of one or more desired categories of use (CI) of requested personalinformation (PI), and/or information resolvable to one or more desiredcategories of use (CI) of requested personal information (PI). As anon-limiting example, as further described herein, regarding FIGS. 2-5and 20, for example, various disclosed embodiments can adhere to apredefined or predetermined taxonomy of categories of use (CI) of PI forthe purposes of storing and accessing blocks and block chains ofpersonal information (PI) stored in DFS. Accordingly, as depicted inFIG. 11, exemplary request 1104 can comprise or be associated with oneor more categories of use (CI), according to the predefined orpredetermined taxonomy of categories of use (CI) of personal information(PI). In a further non-limiting example, exemplary request 1104 cancomprise or be associated with information resolvable to one or morecategories of use (CI), according to the predefined or predeterminedtaxonomy of categories of use (CI) of personal information (PI).

As a non-limiting example, a first exemplary request 1104 might compriseor be associated with information such as one or more of the words“financing,” “auto,” “rates,” “APR,” etc., which can be resolvable toone or more categories of use (CI), such as, but not limited to,financing, auto financing, an offer of sale, etc. In anothernon-limiting example, a second exemplary request 1104 might comprise orbe associated with information such as one or more of the words“hiring,” “benefits,” “skills,” “experience,” etc., which can beresolvable to one or more categories of use (CI), such as, but notlimited to, hiring, invitations to apply to jobs, job offers, etc.

As described above regarding FIG. 10, FIG. 11 depicts the capability ofexemplary requests, such as depicted with respect to exemplary request1104, according to various non-limiting aspects as described herein, tocomprise or be associated with further information such asencryption/decryption keys, timestamp, offer terms, digital signatures,data used terms, other information, and so on, without limitation.However, as further described, regarding FIG. 10, listing of suchcapability should not be construed as requirements and every requestaccording to various non-limiting embodiments described herein. Forinstance, not every request such as exemplary request 1104 wouldcomprise or be associated with an offer, which would include offerterms, would require encrypted responses, and so on. As further depictedin FIG. 11, exemplary request 1104 can comprise or be associated withparticularly identifiable personal information (PI), whether comprisedin exemplary request 1104, or ancillary thereto.

In addition, as further described above regarding FIG. 7, exemplaryprocesses 700 can comprise, at 712, sending encrypted response torequestor, which is depicted in FIG. 11, via off-page reference, E,1106. As further described herein, FIG. 11 depicts receiving encryptedresponse from an access authority (e.g., user 102, one or more devicesor systems operating on behalf of user 102, such as an appropriatelyconfigured app on a device associated with user 102, in communicationwith a device or system 2000, 2200, 2300, portions thereof, etc.) viaoff-page reference F, 1108, at 1110.

For example, FIG. 12 depicts an exemplary response 1202 (e.g., anauthorization) granted by access authority (e.g., user 102, one or moredevices or systems operating on behalf of user 102, such as anappropriately configured app on a device associated with user 102, incommunication with a device or system 2000, 2200, 2300, portionsthereof, etc.). For example, as further described above regardingexemplary processes 700 of FIG. 7, exemplary processes 700 can comprise,at 710, encrypting a hash (e.g., a cryptographic hash, etc.) of the lastsubsequent block 1002 of personal information (PI) (e.g., PI BLOCK(n)[PII+OPI+SI]) and a link or URI returned (e.g., as a result ofstorage in the DFS), as determined at 704, for example. Thus, theexemplary response 1202, properly authorized and granted, can direct therequestor to the last subsequent block 1002 of personal information (PI)(e.g., PI BLOCK (n)[PII+OPI+SI]) via the link or URI returned (e.g., asa result of storage in the DFS). As a non-limiting example, exemplaryresponse 1202 can be encrypted with the requestor's public key, with thesender's private key, and/or using another agreed-upon encryptionprotocol, without limitation.

In a further non-limiting aspect, exemplary response 1202 can furthercomprise the identity of a verifying entity 110 and/or a verifyingentity 110 digital signature, that can facilitate certifying thevalidity of the personal information (PI) associated with one or moreblocks of one or more block chains of personal information (PI) storedin DFS, or portions thereof (e.g., last subsequent block 1002 ofpersonal information (PI) (e.g., PI BLOCK (n)[PII+OPI+SI])), forexample, as further described above, regarding supplemental information(SI) in last subsequent block 1002 of personal information (PI) (e.g.,PI BLOCK (n)[PII+OPI+SI]) and FIG. 10. As non-limiting examples, variousembodiments as described herein can comprise various portions ofsupplemental information (SI) (e.g., in exemplary response 1202, whichcan direct requestor to last subsequent block 1002 of personalinformation (PI) (e.g., PI BLOCK (n)[PII+OPI+SI])) comprising otherauthorization information (OAI), as described above, a hash (e.g., acryptographic hash) of the last subsequent block 1002 of personalinformation (PI) (e.g., PI BLOCK (n)[PII+OPI+SI]) stored in DFS (e.g.,HASH OF PI BLOCK (n)[PII+OPI+SI]), a URI or link of the last subsequentblock 1002 of personal information (PI)(e.g., URI/LINK OF PI BLOCK(n)[PII+OPI+SI]), a verifying entity associated with personalinformation (PI) in or associated with the block (e.g., VERIFYINGENTITY), a verifying entity digital signature associated with personalinformation (PI) in or associated with the block (e.g., VERIFYING ENTITYDIGITAL SIGNATURE), encryption/decryption keys, if any, to facilitatedecryption of personal information (PI) stored in one or more blocks ofthe one or more block chains of personal information (PI) stored in DFS(e.g., ENCRYPTION/DECRYPTION KEY(S)), and so on, without limitation, forexample, as further described herein, regarding FIGS. 9-10. As a furthernon-limiting example, supplemental information (SI) comprising one ormore encryption/decryption keys, if any, to facilitate decryption ofpersonal information (PI) stored in one or more blocks of the one ormore block chains of personal information (PI) stored in DFS (e.g.,ENCRYPTION/DECRYPTION KEY(S)) can be employed to facilitate decryptingone or more blocks of personal information (PI) stored in DFS, accordingto a predetermined encryption protocol or agreement between a user 102and a requestor, for example, comprising a data consumer 106, and/or viaone or more devices or systems acting on their behalf, in furthernon-limiting aspects.

For instance, FIG. 13 depicts a flow diagram of non-limiting aspects ofexemplary processes 1300 for decryption and processing of one or moreuser information or data block chains, according non-limiting aspects ofembodiments of the disclosed subject matter. Having received exemplaryresponse 1202, via off-page reference F, 1108, exemplary processes 1300can comprise decrypting exemplary response 1202, if necessary at 1302.As described above, exemplary response 1202 can be encrypted with therequestor's public key, with the sender's private key, and/or usinganother agreed-upon encryption protocol, without limitation, in variousnon-limiting aspects. Having thus decrypted exemplary response 1202,exemplary processes 1300 can comprise determining one or more hashes(e.g., cryptographic hashes) of one or more last or last subsequentblocks 1002 of one or more personal information (PI) block chains storedin DFS, the associated URI's or links thereto, and other authorizationinformation (OAI), if any, in exemplary response 1202.

In a further non-limiting aspect, exemplary processes 1300 can furthercomprise, at 1306, retrieving one or more last or last subsequent blocks1002 of one or more personal information (PI) block chains, via oraccording to the associated URI's or links thereto, and/or according toother authorization information (OAI), if any, in exemplary response1202, from DFS as indicated via off-page reference G, 1308. Accordingly,in still another non-limiting aspect, exemplary processes 1300 canfurther comprise, at 1310, processing one or more personal information(PI) block chains and other authorization information (OAI), if any,retrieved from DFS as indicated via off-page reference H, 1312 andoff-page reference I, 1314.

For instance, FIG. 14 illustrates exemplary processes 1400 foriteratively processing exemplary response 1202 and one or more personalinformation (PI) block chains stored in DFS, according to variousnon-limiting aspects. For instance, FIG. 14 depicts off-page referenceF, 1108, associated with exemplary response 1202, which facilitatesdirecting requestor to last or last subsequent block 1002 of personalinformation (PI)(e.g., URI/LINK OF PI BLOCK (n)[PII+OPI+SI]), which isprocessed, according to off-page reference G, 1308, as described aboveregarding FIG. 13. In addition, FIG. 14 depicts off-page reference H,1312, which represents retrieving immediately prior subsequent block1004 (e.g., PI BLOCK(n−1)[PII+OPI+SI]), after retrieving, anddecrypting, if any, last or last subsequent block 1002 of personalinformation (PI)(e.g., URI/LINK OF PI BLOCK (n)[PII+OPI+SI]),iteratively through to root block 1006 (e.g., PI BLOCK(0)[PII+OPI+SI]),and off-page reference I, 1314.

Accordingly, FIGS. 13-14 illustrate an exemplary iterative process forprocessing one or more personal information (PI) block chains stored inDFS, which can be generally characterized as a process of, receiving anddecrypting, if any, exemplary response 1202, locating, retrieving, anddecrypting, if any, last or last subsequent block 1002 of personalinformation (PI)(e.g., URI/LINK OF PI BLOCK (n)[PII+OPI+SI]), locating,retrieving, and decrypting, if any, immediately prior subsequent block1004 (e.g., PI BLOCK(n−1)[PII+OPI+SI]), and so on, until locating,retrieving, and decrypting, if any, root block 1006 (e.g., PIBLOCK(0)[PII+OPI+SI]), according to various non-limiting aspects, asdescribed herein, regarding FIGS. 1-12.

In a further non-limiting implementation, FIG. 15 illustrates anexemplary flow diagram of methods 1500 directed to a use of userinformation or data block chains according non-limiting aspects ofembodiments of the disclosed subject matter.

As a non-limiting example, exemplary methods 1500 can comprise, at 1502,storing, by a device comprising a processor (e.g., device or system2000, 2200, 2300, portions thereof, etc.), machine-executable codeassociated with an offer, wherein the offer is contingent upon access topersonal information stored in a set of a plurality of block chains,wherein the plurality of block chains are based on a determined categoryof use of personal information in each of the plurality of block chains,as further described herein, regarding FIGS. 6-14, 15-19, and 20-26, forexample.

In another non-limiting example, exemplary methods 1500 can comprise, at1504, determining, by the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), the determined category of use ofpersonal information, as further described herein, regarding FIGS. 6-14,15-19, and 20-26, for example.

In a further non-limiting example, exemplary methods 1500 can comprise,at 1506, transmitting a request for authorization to access personalinformation and the determined category of use associated with therequest for authorization, as further described herein, regarding FIGS.6-14, 15-19, and 20-26, for example.

According to yet another non-limiting example, exemplary methods 1500can comprise, at 1508, receiving, via the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), one or more cryptographichash associated with a last block of one or more block chain(s) and alink to the last block of the one or more block chain(s) stored in adistributed file system (DFS), as further described herein, regardingFIGS. 6-14, 15-19, and 20-26, for example. According to a non-limitingaspect, exemplary methods 1500 can comprise receiving, via the device(e.g., device or system 2000, 2200, 2300, portions thereof, etc.), anencrypted response and decrypting, via the device (e.g., device orsystem 2000, 2200, 2300, portions thereof, etc.), the encrypted responsecomprising the last block of one or more block chain(s) and the link tothe last block of the one or more block chain(s) stored in a distributedfile system.

In another non-limiting example, exemplary methods 1500 can comprise, at1510, determining, by the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), that the one or more block chain(s) doesnot comprise one or more responsive block chain responsive to the offer,as further described herein, regarding FIGS. 6-14, 15-19, and 20-26, forexample.

In still another non-limiting example, exemplary methods 1500 cancomprise, at 1512, transmitting, by the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), a follow-up request foradditional authorization to access personal information, as furtherdescribed herein, regarding FIGS. 6-14, 15-19, and 20-26, for example.

According to another non-limiting example, exemplary methods 1500 cancomprise, at 1514, determining, by the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), that the one or more blockchain(s) comprises the one or more responsive block chain comprisingpersonal information responsive to the offer, as further describedherein, regarding FIGS. 6-14, 15-19, and 20-26, for example.

FIG. 16 illustrates another flow diagram of further non-limiting aspectsof exemplary methods 1600 for using user information or data blockchains according non-limiting aspects of embodiments as disclosedherein.

As a non-limiting example, exemplary methods 1600 can comprise, at 1602,determining, by the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), based on the offer, a plurality of one or moredata requirements associated with personal information, one or morecontract requirement associated with the offer, one or more successaction defined by the offer, or one or more failure action defined bythe offer, as further described herein, regarding FIGS. 5-15, 17-19, and20-26, for example. Such requirements may include data requirements thatlimit the provision of personal information in connection with theoffer, but may permit the provision of alternative data based upon suchpersonal information in a manner that permits the contracting parties todetermine compliance with a contract provision without accessing thepersonal information. This may be provided through a score,authorization, verification, or other method that may be generatedindependently by a self-executing contract or may be generated by amutually trusted third party. For example, a social security number maybe provided to a mutually trusted third party who returns an indicationof compliance with a contract requirement without the need for thesharing of the social security number between the contracting parties.

In a further non-limiting example, exemplary methods 1600 can comprise,at 1604, comparing, by the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), the one or more responsive block chaincomprising personal information to information associated with theoffer, as further described herein, regarding FIGS. 5-15, 17-19, and20-26, for example.

In yet another non-limiting example, exemplary methods 1600 cancomprise, at 1606, determining, by the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), that one or more of the oneor more data requirement associated with personal information or the oneor more contract requirement associated with the offer is not satisfiedby the one or more responsive block chain comprising personalinformation, as further described herein, regarding FIGS. 5-15, 17-19,and 20-26, for example.

According to a further non-limiting example, exemplary methods 1600 cancomprise, at 1608, transmitting, via the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), the follow-up request foradditional authorization to access personal information, as furtherdescribed herein, regarding FIGS. 5-15, 17-19, and 20-26, for example.

In a further non-limiting example, exemplary methods 1600 can comprise,at 1610, determining, by the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), that the one or more data requirementassociated with personal information and the one or more contractrequirement associated with the offer are satisfied by the one or moreresponsive block chain comprising personal information, as furtherdescribed herein, regarding FIGS. 5-15, 17-19, and 20-26, for example.In a non-limiting aspect of exemplary methods 1600, the determining thatthe one or more data requirement associated with personal information issatisfied can comprise determining, via the device (e.g., device orsystem 2000, 2200, 2300, portions thereof, etc.), one or more ofpersonal information comprising personal identification information orother personal information satisfies the one or more data requirementassociated with personal information, wherein the personalidentification information is defined as information or combinations ofinformation that resolve to a unique user, meeting or exceeding apredetermined threshold confidence level, and wherein the other personalinformation is defined as other information or combinations of otherinformation that does not resolve to the unique user, by failing to meetor exceed the predetermined threshold confidence level, and wherein theone or more block chain(s) is based on at least the personalidentification information.

As a further non-limiting example, exemplary methods 1600 can comprise,at 1612, executing, by the device (e.g., device or system 2000, 2200,2300, portions thereof, etc.), based on the offer, one or more of theone or more success action defined by the offer or the one or morefailure action defined by the offer, as further described herein,regarding FIGS. 5-15, 17-19, and 20-26, for example.

In still further non-limiting examples, exemplary methods as describedherein can comprise one or more of retrieving, by the device (e.g.,device or system 2000, 2200, 2300, portions thereof, etc.), the lastblock of the one or more block chain(s) via link to the last block ofthe one or more block chain(s) stored in the DFS, determining, by thedevice (e.g., device or system 2000, 2200, 2300, portions thereof,etc.), other authorization information associated with the one or moreblock chain(s), and/or processing, by the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), the one or more blockchain(s) to determine personal information. In a non-limiting aspect ofexemplary methods as described herein, the processing the one or moreblock chain(s) to determine personal information can comprisedetermining, via the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), a plurality of a cryptographic hash of a priorblock of personal information associated with the one or more blockchain(s), a link to the prior block of personal information associatedwith the one or more block chain(s) stored in the DFS, a verifyingentity associated with the personal information, a digital signatureassociated with the verifying entity, or information associated with anencryption key or decryption key.

In still further non-limiting aspects of exemplary methods as describedherein, can further comprise the determining, by the device (e.g.,device or system 2000, 2200, 2300, portions thereof, etc.), that one ormore limitation associated with the other authorization informationspecified in the one or more block chain(s) is satisfied. In anon-limiting aspect of exemplary methods as described herein, thedetermining that the one or more limitation associated with the otherauthorization information specified is satisfied can comprise executing,by the device (e.g., device or system 2000, 2200, 2300, portionsthereof, etc.), machine-executable code associated with the offer anddefined by the one or more limitation associated with the otherauthorization information comprising one or more term of use associatedwith the personal information, including one or more of an expirationterm for one or more of the authorization or the personal information, avalidity term associated with the personal information, one or more of apayee or a requested fee associated with the one or more of theauthorization or the personal information, one or more of a transmissionlimit or a storage limit associated with the one or more of theauthorization or the personal information, or a restriction associatedwith the one or more of the authorization or the personal information ona third party.

As further described herein, various operations and/or processes can beundertaken by one or more devices or systems on behalf of, for example,one or more user 102, one or more data consumer 106 (e.g., a requestor),one or more verifying entities 110, and so on, without limitation. Asnon-limiting examples, FIGS. 17-19 illustrate flow diagram ofnon-limiting aspects of exemplary processes for use of user data blockchains according non-limiting aspects of embodiments of the disclosedsubject matter. As described above regarding FIGS. 15-16, for instance,various operations and/or processes as described regarding FIGS. 17-19via one or more devices or systems (e.g., device or system 2000, 2200,2300, portions thereof, etc.), on behalf of one or more user 102, one ormore data consumer 106 (e.g., a requestor), one or more verifyingentities 110, and so on. Moreover, many operations and/or processes ofFIGS. 17-19 have been described above, and thus, where operations havebeen described above, the operations and/or processes of FIGS. 17-19 canbe described by reference to prior descriptions.

For instance, FIG. 17 depicts exemplary processes 1700 which cancomprise, at 1702, storing, by a device comprising a processor (e.g.,device or system 2000, 2200, 2300, portions thereof, etc.),machine-executable code associated with an offer, wherein the offer iscontingent upon access to personal information stored in a set of aplurality of block chains, wherein the plurality of block chains arebased on a determined category of use of personal information in each ofthe plurality of block chains, as further described herein, regardingFIGS. 11, 13, and 15-16, for example. Thus, at 1702, exemplary processes1700 can comprise receiving and/or storing an offer (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.), which is contingent onaccess to personal information contained in one or more personalinformation (PI) block chains (e.g., stored in DFS), wherein the one ormore personal information (PI) block chains in DFS base on one or morecategories of use (CI). According to further non-limiting aspects, theoffer can be further processed via off-page reference J, 1704, asfurther described, regarding FIG. 19.

After an offer contingent on access to personal information (PI)contained in one or more personal information (PI) block chains storedin DFS based on one or more desired categories of use (CI) are receivedand/or stored at 1702, exemplary processes 1700 can comprise, at 1704,determining, by the device (e.g., device or system 2000, 2200, 2300,portions thereof, etc.), the determined category of use of personalinformation (PI), as further described herein, regarding FIGS. 6, 8, 11,15, etc., for example. In a non-limiting aspect, a determined categoryof use of personal information (PI) can be explicitly stated or based oninformation resolvable to category of use of personal information (PI),for example, as described above regarding exemplary request 1104. Infurther non-limiting aspects, exemplary processes 1700 can comprisesending a request to authorize access to one or more personalinformation (PI) block chain based on one or more desired categories ofuse (CI), for example, such as described above regarding exemplaryprocesses 1100, at 1102, which may also proceed from off-page referenceK, 1708, of FIG. 19. In still further non-limiting aspects, exemplaryprocesses 1700 can comprise receiving an encrypted response from anaccess authority, for example, such as described above regardingexemplary processes 1100, at 1110, which may also proceed from off-pagereference F, 1108, of FIG. 11, and can further comprise decrypting theresponse (e.g., exemplary response 1202), for example, such as describedabove regarding exemplary processes 1302, at 1110, and can proceed viaoff-page reference L, 1710, of FIG. 18.

FIG. 18 depicts exemplary processes 1800, which, proceeding via off-pagereference L, 1710, and having thus decrypted exemplary response 1202,exemplary processes 1800 can comprise, at 1304, determining one or morehashes (e.g., cryptographic hashes) of one or more last or lastsubsequent blocks 1002 of one or more personal information (PI) blockchains stored in DFS, the associated URI's or links thereto, and otherauthorization information (OAI), if any, in exemplary response 1202, asfurther described above regarding FIG. 13.

In a further non-limiting aspect, exemplary processes 1800 can furthercomprise, at 1306, retrieving one or more last or last subsequent blocks1002 of one or more personal information (PI) block chains, via oraccording to the associated URI's or links thereto, and/or according toother authorization information (OAI), if any, in exemplary response1202, from DFS, as further described above regarding FIG. 13.Accordingly, in still another non-limiting aspect, exemplary processes1800 can further comprise, at 1310, processing one or more personalinformation (PI) block chains and other authorization information (OAI),if any, retrieved from DFS, as further described above regarding FIG.13.

In still another non-limiting aspect, exemplary processes 1800 canfurther comprise, at 1802, determining whether all authorized personalinformation (PI) block chains have been processed, received via off-pagereference M, 1804, to FIG. 19, if all authorized personal information(PI) block chains have been processed, and proceeding back to exemplaryprocesses 1800, at 1306, to retrieve further authorized personalinformation (PI) blocks and/or block chains (e.g., authorized blocks,block chains, side chains, etc.) from DFS, if not all authorizedpersonal information (PI) block chains have been processed, at 1802.

FIG. 19 depicts exemplary processes 1900, which, proceeding via off-pagereference J, 1704, and having received and/or stored offer (e.g., viadevice or system 2000, 2200, 2300, portions thereof, etc.), at 1702, cancomprise, at 1902, determining, by the device (e.g., device or system2000, 2200, 2300, portions thereof, etc.), based on the offer, aplurality of one or more data requirements associated with personalinformation, one or more contract requirement associated with the offer,one or more success action defined by the offer, or one or more failureaction defined by the offer, as further described herein, regarding FIG.16, for example, which can be stored (e.g., via device or system 2000,2200, 2300, portions thereof, etc.), at 1904, for subsequent referenceand/or use. For example, exemplary data requirements of personalinformation (PI) specified in the offer can typically comprise requestfor personal information, such as might appear in an application (e.g.,name, address, date of birth, phone number, email address, accountinformation, current employer, prior employer(s), username(s),password(s), etc.), for example, as further described above regardingFIGS. 3-4, without limitation. As a further non-limiting example,exemplary contract requirements associated with the offer can typicallycomprise if/then logic or requirements of the personal informationpursuant to terms of a prospective contract (e.g., income level, accountbalance(s), employment eligibility data requirements, insurancerequirements, etc.), that can be employed to facilitate determiningwhether the various portions of personal information (PI) comprised inthe one or more personal information (PI) block chain stored in DFS,authorized and/or obtainable (e.g., via one or more third party dataproviders 104, e.g., via subsequent or follow-up exemplary requests1104, etc.) meet the one or more exemplary contract requirementsassociated with the offer, without limitation.

In a further non-limiting aspect, the one or more success actionsdefined by the offer and the one or more failure action(s) defined bythe offer, can comprise one or more actions to be taken (e.g., asdefined in the offer, as defined in the supplemental information (SI),other authorization information (OAI), other information, etc.), in theevent that is determined that the one or more data requirementsassociated with personal information and the one or more contractrequirement associated with the offer are met, as further describedherein, regarding FIG. 16, at 1610, for example. As a non-limitingexample, upon meeting or not meeting the one or more data requirementsassociated with personal information and the one or more contractrequirement associated with an offer for credit or financing, the one ormore success actions defined by the offer and the one or more failureaction(s) defined by the offer, as the case may be, can includeextension of credit or financing, transmitting a conditional approval,etc., or a denial thereof, retention of personal information (PI)obtained in the described processes, or expungement thereof, and so on,respectively, without limitation. As a further non-limiting example,upon meeting or not meeting the one or more data requirements associatedwith personal information and the one or more contract requirementassociated with an offer to apply to a prospective employer foremployment, the one or more success actions defined by the offer and theone or more failure action(s) defined by the offer, as the case may be,can include transmitting an invitation for an interview, transmitting arequest for further information, or transmitting a rejection letter,retention of personal information (PI) obtained in the describedprocesses, or expungement thereof, and so on, respectively, withoutlimitation.

Accordingly, exemplary processes 1900 can further comprise, at 1906,determining whether the one or more data requirements of personalinformation (PI) specified in the offer are met. If not, and if it isdetermined that third party data requests are authorized (e.g., viaother authorization information OAI in an exemplary response 1202,and/or one or more personal information (PI) blocks stored in DFS,etc.), at 1908, exemplary processes 1900 can further comprise, at 1910,one or more of requesting, receiving, and/or storing (e.g., via deviceor system 2000, 2200, 2300, portions thereof, etc.) third party data(e.g., via one or more exemplary data provider(s) 104, etc.). If not,and if it is determined that third party data requests are notauthorized (e.g., via other authorization information OAI in anexemplary response 1202, and/or one or more personal information (PI)blocks stored in DFS, etc.), at 1908, exemplary processes 1900 canfurther comprise sending a request to authorize access to one or morepersonal information (PI) block chain based on one or more desiredcategories of use (CI), for example, such as described above regardingexemplary processes 1100, at 1102, proceeding via off-page reference K,1708, to FIG. 17, which then proceeds through exemplary processes 1800,to ensure all authorize personal information block chains are processed,as described above, and proceeding via off-page reference M, 1804, toFIG. 19, where exemplary processes 1900 can further comprise, at 1900,determining whether the other authorization information (OAI)limitations of the personal information (PI) of the one or more personalinformation blocks stored in DFS are met.

As described above, exemplary processes 1900 can further comprise, at1906, determining whether the one or more data requirements of personalinformation (PI) specified in the offer are met. If it is determined, at1906, that the one or more data requirements of personal information(PI) specified in the offer are met, then, exemplary processes 1900 canfurther comprise, at 1914, determining whether the contract requirementsof the personal information (PI) of the one or more personal information(PI) blocks stored in DFS is met, in a further non-limiting aspect, asfurther described herein. If either the contract requirements of thepersonal information (PI) of the one or more personal information (PI)blocks stored in DFS, at 1914, or the other authorization information(OAI) limitations of the personal information (PI) of the one or morepersonal information blocks stored in DFS, at 1912, are not met, then,at 1916, exemplary processes 1900 can further comprise determining thatthe potential contract (e.g., as governed by the offer data requirementsof personal information (PI), the contract requirements, and/or theother authorization information (OAI), etc.) has failed and can beclassified as a contract failure, and can further comprise, at 1918,executing the one or more contract failure actions, as further describedherein. Alternatively, if the contract requirements of the personalinformation (PI) of the one or more personal information (PI) blocksstored in DFS, at 1914, the other authorization information (OAI)limitations of the personal information (PI) of the one or more personalinformation blocks stored in DFS, at 1912, and the one or more datarequirements of personal information (PI) specified in the offer, at1906, are met, then, at 1920, exemplary processes 1900 can furthercomprise determining that the potential contract (e.g., as governed bythe offer data requirements of personal information (PI), the contractrequirements, and/or the other authorization information (OAI), etc.)has succeeded and can be classified as a contract success, and canfurther comprise, at 1922, executing the one or more contract successactions, as further described herein.

As further described herein, in various non-limiting embodimentsdescribed herein, the one or more processes or process steps asdescribed can be performed by one or more devices or systems (e.g., viadevice or system 2000, 2200, 2300, portions thereof, etc.), and/orportions are combinations thereof, on behalf of the entities describedherein, regarding FIG. 1 and exemplary environment 100, for example,including, but not limited to one or more user(s) 102, one or more dataprovider(s) 104, one or more data consumer(s) 106, one or more datasources 108, and/or one or more verifying entities 110, either on whollyautomated, partially automated, or interactive basis, with or withoutintervention required by one or more of the entities described herein,regarding FIG. 1 and exemplary environment 100.

Accordingly, FIG. 20 depicts a functional block diagram illustratingexemplary non-limiting devices or systems suitable for use with aspectsof the disclosed subject matter. For instance, FIG. 20 illustratesexemplary non-limiting devices or systems 2000 suitable for performingvarious aspects of the disclosed subject matter in accordance with anexemplary data safe or user data safe 112 as further described herein.For example, as described above regarding FIG. 1, a user 102 caninteract with data safe or user data safe 112 via a front-end system2002 that can comprise or be associated with one or more communicationcomponents and/or one or more user interface components 2004. As furtherdescribed herein, user 102 interactions with data safe or user data safe112 can be further processed and/or handled via a back-end system 2006that can also comprise or be associated with system management layer2016 and/or one or more system components. As depicted in FIG. 20, datasafe or user data safe 112 can comprise a front-end system 2002 thatcan, in turn, comprise one or more of mobile data communicationcomponent 2008, phone communication component 2010, web communicationcomponent 2012, and/or other media communication component 2014, etc. Asfurther depicted in FIG. 20, data safe or user data safe 112 cancomprise a back-end system 2006 that can, in turn, comprise one or moreof host processor 2018, storage component 2020, data managementcomponent 2022, authorization component 2024, cryptographic component2026, contract management component 2028, etc., either as describedabove, or as further described herein.

For instance, as described above, data safe or user data safe 112 canfacilitate user 102 interaction with data safe or user data safe 112 viafront-end system 2002 to enable input of information into data safe oruser data safe 112 and/or receipt of information out of data safe oruser data safe 112 associated with information processing, handling,and/or transformation occurring within data safe or user data safe 112or otherwise. In a non-limiting implementation of data safe or user datasafe 112 comprising an exemplary mobile data communication component2008, data safe or user data safe 112 can facilitate transmittinginformation to, and/or receiving information from, data safe or userdata safe 112 via one or more devices configured to transmit and receiveinformation via a wireless data network (e.g., cellular wireless,Wireless Fidelity (WiFi™), Worldwide Interoperability for MicrowaveAccess (WiMax®), etc.). In yet other non-limiting implementations ofdata safe or user data safe 112 comprising an exemplary phonecommunication component 2010, data safe or user data safe 112 canfacilitate transmitting information to, and/or receiving informationfrom, data safe or user data safe 112 via one or more devices configuredto transmit and receive information via a voice network (e.g., cellularwireless voice network, analog or digital fixed line network, such asvia conventional land-line networks, etc.). In further non-limitingimplementations of data safe or user data safe 112 comprising anexemplary web communication component 2012, data safe or user data safe112 can facilitate transmitting information to, and/or receivinginformation from, data safe or user data safe 112 via one or moredevices configured to transmit and receive information via a datanetwork supporting conventional web browsing protocols and/orapplications (e.g., such as via a data connected device connected to anintranet, the Internet, wireless networks, etc.).

In still other exemplary implementations of data safe or user data safe112 comprising other media communication component 2014, data safe oruser data safe 112 can facilitate transmitting information to, and/orreceiving information from, data safe or user data safe 112 via one ormore devices configured to transmit and receive information via othertechnologies (e.g., mesh networks, ad hoc networks, personal areanetworks, interactive television, wearable computing devices, facialrecognition, video telephony via any of a number of networks includingthe Internet, wireless networks, etc., near field communications (NFC)techniques including communications protocols and data exchange formats,such as those based on radio-frequency identification (RFID) techniques,quick response codes (QR Codes®), barcodes, voice recognition, etc.),without limitation.

At this point, it should be noted that, while a number of componentsand/or systems are depicted in FIG. 20, and/or are described herein withrespect to data safe or user data safe 112 comprising various componentsand/or systems, various non-limiting implementations of data safe oruser data safe 112 and/or devices associated with a user 102 that cancomprise and/or interact with data safe or user data safe 112 are not solimited. For instance, it can be understood that, depending on thecontext of the user 102 (or other entity, for example, as describedabove regarding FIG. 1 and exemplary operating environment 100)interaction with data safe or user data safe 112 and/or a device orsystem associated with a user 102 (or other entity), such a device orsystem associated with a user 102 (or other entity) can comprise any ofa number of components, subcomponents, and/or portions thereof depictedin FIG. 20, and/or can comprise such components, subcomponents, and/orportions thereof in lieu of, in addition to, and/or complementary tocomponents depicted in FIG. 20. As a non-limiting example, a device(e.g., such as a mobile device) associated with user 102 can comprise auser interface and/or a web browser, subcomponents, and/or portionsthereof that are complementary (e.g., that can serve as a client of aserver) to user interface component 2004 of various implementations datasafe or user data safe 112 (e.g., that serve as the server to theclient). In a further non-limiting example, a device (e.g., such as amobile device) associated with user 102 can comprise any of a number ofcomponents, subcomponents, and/or portions thereof that can be employedin lieu of (or at least partially in lieu of) components depicted inFIG. 20 (e.g., such as an application, or app, programmed in native codefor the particular device, etc.) that accomplishes and/or facilitatesfunctionalities, or portions thereof, associated with componentsdepicted in FIG. 20.

Thus, FIG. 20 illustrates an exemplary non-limiting device or system2000 suitable for performing various aspects of the disclosed subjectmatter regarding the provision, the collection, the use, and thedistribution of user information about user 102, as well as thevalidation, the verification, the authentication, and the properprotection and control of such user information about user 102, toensure smooth, efficient, and cost-effective business processes, andtherefore, in turn, attractive prices on the offered goods and servicesin accordance with the various non-limiting embodiments as describedherein.

For instance, as described below with reference to FIG. 21, for example,various non-limiting embodiments of the disclosed subject matter cancomprise more or less functionality than those exemplary devices orsystems described therein, depending on the context. In addition, adevice or system 2000 as described can be any of the devices and/orsystems as the context requires and as further described above inconnection with FIGS. 1-19. It can be understood that while thefunctionality of device or system 2000 is described in a general sense,more or less of the described functionality may be implemented,combined, and/or distributed (e.g., among network components, servers,databases, and the like), according to context, system designconsiderations, and/or marketing factors, and the like. For the purposesof illustration and not limitation, exemplary non-limiting devices orsystems 2000 can comprise one or more exemplary devices and/or systemsof FIG. 21, such as data safe or user data safe 112 (or device 2110,computing system 2126, computing system 2130, etc.) as described below,for example, or portions thereof.

In yet another non-limiting example, data safe or user data safe 112 canbe implemented a subset of components associated with data safe or userdata safe 112 and/or portions thereof can be incorporated within,associated with, in communication with, and/or otherwise affiliated withanother computing system (e.g., such as one or more of a social medianetwork computing system, a governmental agency network computingsystem, a search network computing system, etc.), and/or one or morecomputing systems associated with third parties, (e.g., individuals,political organizations, employment agencies organizations, serviceproviding organizations, etc.). Moreover, any of the componentsdescribed herein can be configured to perform the describedfunctionality (e.g., via computer-executable instructions stored in atangible computer readable medium, and/or executed by a computer, aprocessor, etc.). Additionally, it can be understood that variouscomponents, as described herein, can be communicatively coupled with oneor more other components, as described herein, or otherwise, to sharedata and/or information among such components to accomplish anyfunctionality, as described herein, and/or otherwise, that can beassociated with data safe or user data safe 112, related thereto, and/orancillary to various aspects and disclosed subject matter.

Referring again to FIG. 20, data safe or user data safe 112 comprisingdevice or system 2000, or portions thereof, can also include a userinterface component 2004, which can be associated with one or more hostprocessors 2018, and which can facilitate various aspects of thedisclosed subject matter. For instance, user interface component 2004can provide various types of user interfaces to facilitate interactionbetween a user 102 (e.g., user 102, a device on behalf of user 102, anappropriately configured application, or app, such as an appappropriately configured for a specific device, such as described belowwith reference to FIGS. 21-26) and any component coupled to, orassociated with, one or more host processors 2018, data safe or userdata safe 112, and so on, for example, such as described below withreference to FIGS. 21-26, etc. In addition to being configured oradapted to be accessed by one or more user 102, user interface component2004, can be further configured to provide one or more GUIs, commandline interfaces (CLIs), machine accessible interfaces (e.g., APIs suchas e-commerce and/or MIS back-end interfaces), structured and/orcustomized menus, and the like. In yet another exemplary implementation,user interface component 2004 can facilitate interaction between a user102 (e.g., via a device associated with user 102, etc.), such as betweena mobile device native app installed directly onto the device (e.g.,smartphone, tablet, etc.) coded in its own native programming language,and/or a mobile web app (e.g., an Internet-enabled app, etc.) that hasspecific functionality for mobile devices and accessed through themobile device's web browser, as further described herein.

For example, an exemplary data safe or user data safe 112 comprisinguser interface component 2004 can facilitate rendering a GUI that canprovide user 102 with a region (e.g., region of a device screen, such asvia an operating system (OS), application, or otherwise, etc.) or othermeans to load, import, read, etc., data and/or information, and/or caninclude a region to present results output from data safe or user datasafe 112. These regions can comprise known text and/or graphic regionscomprising dialogue boxes, static controls, drop-down-menus, list boxes,pop-up menus, edit controls, combo boxes, radio buttons, check boxes,push buttons, and/or graphic boxes, and the like. In addition, utilitiesto facilitate the presentation such as vertical and/or horizontal scrollbars for navigation and toolbar buttons to determine whether a regionwill be viewable can be employed. For example, user 102 can interactwith one or more of the components depicted in FIG. 20, for instance,whether associated with, coupled to, and/or incorporated in one or morehost processors 2018 associated with data safe or user data safe 112,and so on.

Data safe or user data safe 112 comprising user interface component 2004can facilitate user 102 interaction with such regions to select and/orprovide information via various devices such as a mouse, a roller ball,a keypad, a keyboard, touchpad, touch screen, a pen and/or voiceactivation, for example. Typically, a mechanism such as a push button orthe enter key on the keyboard can be employed to facilitate enteringinformation in a device associated with user 102 to facilitateinteraction with data safe or user data safe 112 comprising device orsystem 2000, or portions thereof. However, it is to be understood thatthe claimed subject matter is not so limited. In a non-limiting example,merely highlighting a check box can initiate information conveyance.

In yet another example, a command line interface (CLI) can be employed.For example, the command line interface can prompt (e.g., via a textmessage on a display and/or an audio tone, etc.) user 102 forinformation via providing a text message. Thus, user 102 can providesuitable information, such as alpha-numeric input corresponding to anoption provided in the interface prompt or an answer to a question posedin the prompt. It is to be understood that a command line interface canbe employed in connection with a GUI and/or API. In addition, thecommand line interface can be employed in connection with hardware(e.g., video cards of a computer) and/or displays (e.g., black andwhite, EGA, or other video display unit of a standalone device such asan LCD display on a network capable device) with limited graphicsupport, and/or low bandwidth communication channels. As a furtherexample, a device associated with user 102 that facilitates interactionwith data safe or user data safe 112 comprising device or system 2000can include one or more motion sensors and associated softwarecomponents, voice activation components, and/or facial recognitioncomponents that can be used by a user to facilitate entering informationinto data safe or user data safe 112 comprising device or system 2000,or portions thereof.

Accordingly, an exemplary data safe or user data safe 112 can compriseor be associated with advanced mobile device centric applications andservices that can facilitate interactions with data safe or user datasafe 112 as described herein related to various functionalities, e.g.,via one or more of user interface component 2004 and/or communicationcomponents, etc. For instance, in an exemplary implementation data safeor user data safe 112 can facilitate user 102 employing any of a varietyof devices comprising an appropriately configured application, or app(e.g., such as via an app appropriately configured for a specific deviceassociated with user 102, an app appropriately configured for acommunications service carrier, etc.), such as described below withreference to FIGS. 21-26). As a result, data safe or user data safe 112can provide one or more of a variety of interfaces to mobile devices viamobile applications that can facilitate providing access to data safe oruser data safe 112 functionalities as described herein, for example,with reference to FIGS. 1-19, etc.

Thus, in exemplary non-limiting implementations, data safe or user datasafe 112 can facilitate user 102 interfacing with data safe or user datasafe 112 via a mobile device, a phone, a web browser, and/or other mediaand/or device types (e.g., via one or more of mobile data communicationcomponent 2008, phone communication component 2010, web communicationcomponent 2012, and/or other media communication component 2014, etc.),which are employed by, or are associated with, user 102. In furthernon-limiting implementations, data safe or user data safe 112 comprisinguser interface component 2004 can facilitate transforming any of avariety of input formats (e.g., data, voice, video, biometric, etc.)into a common data format and/or transmitting input formats and/orcommon data format to back-end system 2006. Moreover, any of thecomponents described herein (e.g., one or more of user interfacecomponent 2004, mobile data communication component 2008, phonecommunication component 2010, web communication component 2012, and/orother media communication component 2014, etc.) can be configured toperform the described functionality (e.g., via computer-executableinstructions stored in a tangible computer readable medium, and/orexecuted by a computer, a processor, etc.).

Referring again to FIG. 20, in further exemplary implementations, datasafe or user data safe 112 can comprise one or more system managementlayers 2016 that can facilitate management of one or more systemcomponents, as further described herein, and/or one or more componentsassociated with user interface component 2004, one or morecommunications components, and so on, for example, viacomputer-executable instructions executing on one or more hostprocessors 2018, or otherwise. In a non-limiting example of an exemplarydata safe or user data safe 112, one or more system components cancomprise one or more of storage component 2020, data managementcomponent 2022, authorization component 2024, cryptographic component2026, contract management component 2028, etc., without limitation. Inaddition to being configured or adapted to facilitate management of oneor more of system components, and so on, system management layer 2016,can be further configured to manage and/or provide one or moreinterfaces such as one or more CLIs, machine accessible interfaces(e.g., APIs such as e-commerce and/or MIS back-end interfaces), and thelike, whether in lieu of, in addition to, and/or complementary to anysuch interfaces provided by user interface component 2004 or othercomponents associated with data safe or user data safe 112.

As described above, an exemplary data safe or user data safe 112comprising device or system 2000, or portions thereof, can include oneor more host processors 2018 that can be associated with one or moresystem components. As a non-limiting example, computer-executableinstructions associated with one or more system components can beexecuted via one or more host processors 2018. For instance, asdescribed above, data safe or user data safe 112 can facilitate user 102(e.g., user 102, a device on behalf of user 102, an appropriatelyconfigured application, or app, such as an app appropriately configuredfor a specific device, etc.) registering a user 102, or a computer ordevice on behalf of user 102, with data safe or user data safe 112, fora service that facilitates interaction with data safe or user data safe112, and so on etc. Moreover, any of the components described herein(e.g., one or more of system management layers 2030, system components,etc.) can be configured to perform the described functionality (e.g.,via computer-executable instructions stored in a tangible computerreadable medium, and/or executed by a computer, a processor, etc.).

For still other non-limiting implementations, data safe or user datasafe 112 comprising device or system 2000, or portions thereof, can alsoinclude storage component 2020 (e.g., which can comprise one or more oflocal storage component, network storage component, such as a networkstorage component associated with DFS, memory 2202, storage component2020, etc.) that can facilitate storage and/or retrieval of data and/orinformation associated with data safe or user data safe 112. Thus, asdescribed above, an exemplary data safe or user data safe 112 comprisingdevice or system 1100, or portions thereof, can include one or more hostprocessors 2018 that can be associated with storage component 2020 tofacilitate storage of data and/or information (e.g., personalinformation (PI), supplemental information (SI), other authorizationinformation (OAI), categories of use (CI), links or URIs, hashes (e.g.,cryptographic hashes), other information, digital signatures, offers,etc.), and/or instructions for performing functions associated withand/or incident to the disclosed subject matter as described herein, forexample, regarding FIGS. 1-19, etc.

In a non-limiting embodiment, exemplary data safe or user data safe 112can comprise or be associated with a storage component 2020 configuredto store personal information (PI) associated with a user (e.g., user102) in a distributed file system (DFS), for example, as furtherdescribed herein, regarding FIGS. 5-14. In a further non-limitingexample, exemplary data safe or user data safe 112 can comprise or beassociated with a storage component 2020 configured to store thepersonal information (PI) with supplemental information (SI) encryptedto facilitate one or more of creation of one or more block chain of thenumber of block chains or determining an applicability status of therequest for authorization (e.g., exemplary request 1104), for example,as further described herein, regarding FIGS. 5-14. In still anothernon-limiting example, exemplary data safe or user data safe 112 cancomprise or be associated with a storage component 2020 configured tostore the personal information (PI) in the DFS comprisinginter-planetary file system (IPFS), for example, as further describedherein, regarding FIGS. 5-14.

In yet another non-limiting embodiment, exemplary data safe or user datasafe 112 can comprise or be associated with a storage component 2020configured to store machine-executable code associated with an offer,wherein the offer can be contingent upon access to personal information(PI) stored in a set of a number of block chains, wherein the number ofblock chains are based on a determined category of use (CI) of personalinformation (PI) in each of the number of block chains, for example, asfurther described herein, regarding FIGS. 15-19.

It can be understood that storage component 2020 can comprise one ormore of system components, and/or portions thereof, to facilitate any ofthe functionality described herein and/or ancillary thereto, such as byexecution of computer-executable instructions by a computer, aprocessor, etc. (e.g., one or more of host processors 2018, processor2204, etc.). Moreover, any of the components described herein (e.g.,storage component 2020, etc.) can be configured to perform the describedfunctionality (e.g., via computer-executable instructions stored in atangible computer readable medium, and/or executed by a computer, aprocessor, etc.).

For still other non-limiting implementations, data safe or user datasafe 112 comprising device or system 2000, or portions thereof, can alsoinclude data management component 2022 that can facilitate creation ofblock chains of personal information (PI), based on a determinedcategory of use (CI) the PI in the block chains, for example, as furtherdescribed herein, regarding FIGS. 5-19, for example, and/or otherfunctionalities associated with data safe or user data safe 112. Thus,as described above, an exemplary data safe or user data safe 112comprising device or system 1100, or portions thereof, can include oneor more host processors 2018 that can be associated with data managementcomponent 2022 to facilitate management of data and/or information(e.g., personal information (PI), supplemental information (SI), otherauthorization information (OAI), categories of use (CI), links or URIs,hashes (e.g., cryptographic hashes), other information, digitalsignatures, offers, etc.), and/or instructions for performing functionsassociated with and/or incident to the disclosed subject matter asdescribed herein, for example, regarding FIGS. 1-19, etc.

In a non-limiting embodiment, exemplary data safe or user data safe 112can comprise or be associated with a data management component 2022configured to create a number of block chains of personal information(PI), based on a determined category of use (CI) of each of the numberof block chains, for example, as further described herein, regardingFIGS. 5-14. In a further non-limiting example, exemplary data safe oruser data safe 112 can comprise or be associated with a data managementcomponent 2022 configured to determine the one or more term of use,comprising one or more of an expiration term for one or more of theauthorization or the personal information (PI), a validity termassociated with the personal information (PI), one or more of a payee ora requested fee associated with the one or more of the authorization orthe personal information (PI), one or more of a transmission limit or astorage limit associated with the one or more of the authorization orthe personal information (PI), or a restriction associated with the oneor more of the authorization or the personal information (PI) on a thirdparty (e.g., one or more of third parties, such as one or more dataprovider(s) 104, one or more data source(s) 108, one or more verifyingentities 110, one or more other data consumer(s) 106, etc.), forexample, as further described herein, regarding FIGS. 5-14.

In another non-limiting example, exemplary data safe or user data safe112 can comprise or be associated with a data management component 2022configured to determine whether the personal information (PI) can bepersonally identifying information or other personal information (PI),wherein the personally identifying information can be defined asinformation or combinations of information that resolve to a unique user(e.g., user 102), meeting or exceeding a predetermined thresholdconfidence level, and wherein the other personal information (PI) can bedefined as other information or combinations of other information thatdoes not resolve to the unique user (e.g., user 102), by failing to meetor exceed the predetermined threshold confidence level, and can befurther configured to create the number of block chains based on atleast the personally identifying information, for example, as furtherdescribed herein, regarding FIGS. 5-14. In still another non-limitingexample, exemplary data safe or user data safe 112 can comprise or beassociated with a data management component 2022 configured to determinefrom the request for authorization (e.g., exemplary request 1104) thedetermined category of use (CI), wherein the data management component2022, can be further configured to determine whether one or moreresponsive block chain exists that can be responsive to the determinedcategory of use (CI) and the request for authorization (e.g., exemplaryrequest 1104) in the set of the number of block chains, and wherein thedata management component 2022 can be further configured to create theone or more responsive block chain if the one or more responsive blockchain does not exist, for example, as further described herein,regarding FIGS. 5-14. As described above regarding FIG. 11, for example,various disclosed embodiments can adhere to a predefined orpredetermined taxonomy of categories of use (CI) of PI for the purposesof storing and accessing blocks and block chains of personal information(PI) stored in DFS. For instance, FIG. 2 is described regarding anexemplary credit lending process, in which various uses are defined thatare applicable to credit lending. However, within such a process, manysubprocesses are described, for which various further categories of use(CI) can be defined (e.g., underwriting, fraud prevention, etc.).Similar categories of use (CI) can be defined for further processes(e.g., employment application and/or verification, insurance eligibilityand/or rate determination, medical service applicability, etc.), withoutlimitation. Moreover, FIGS. 3 and 4 illustrate non-limiting examples ofuser information about a user 102 (e.g., personal information (PI)) thatcan be employed in the provision, collection, use, distribution, and soon, of user information about the user, in accordance with variousembodiments of an exemplary data safe or user data safe 112 as describedherein. Accordingly, such examples of user information about a user 102(e.g., personal information (PI)) can be linked or associated in anexemplary taxonomy with particular categories of use (CI), such as via adatabase, lookup table, and so on (e.g., via exemplary storage component2020) to enable exemplary data management component 2022 determining acategory of use (CI) (e.g., from exemplary request 1104, etc.), tocreate a number of block chains of personal information (PI), based on adetermined category of use (CI), and so on, without limitation. In anon-limiting aspect, various examples of user information about a user102 (e.g., personal information (PI)) can be linked or associated in thepredetermined or predefined taxonomy more than one category of use (CI).

In yet another non-limiting embodiment, exemplary data safe or user datasafe 112 can comprise or be associated with a data management component2022 configured to determine the determined category of use (CI) ofpersonal information (PI), for example, as further described herein,regarding FIGS. 15-19. In a further non-limiting example, exemplary datasafe or user data safe 112 can comprise or be associated with a datamanagement component 2022 configured to retrieve the last block (e.g.,last or last subsequent block 1002) of the one or more block chain vialink to the last block (e.g., last or last subsequent block 1002) of theone or more block chain stored in the DFS, for example, as furtherdescribed herein, regarding FIGS. 15-19.

In another non-limiting example, exemplary data safe or user data safe112 can comprise or be associated with a data management component 2022configured to process the one or more block chain to determine personalinformation (PI), for example, as further described herein, regardingFIGS. 15-19.

In still another non-limiting example, exemplary data safe or user datasafe 112 can comprise or be associated with a data management component2022 configured to determine a number of a cryptographic hash of a priorblock (e.g., immediately prior subsequent block 1004, root block 1006)of personal information (PI) associated with the one or more blockchain, a link to the prior block (e.g., immediately prior subsequentblock 1004, root block 1006) of personal information (PI) associatedwith the one or more block chain stored in the DFS, a verifying entityassociated with the personal information (PI), a digital signatureassociated with the verifying entity, or information associated with anencryption key or decryption key, for example, as further describedherein, regarding FIGS. 15-19.

In a further non-limiting example, exemplary data safe or user data safe112 can comprise or be associated with a data management component 2022configured to determine that one or more limitation associated with theother authorization information (OAI) specified in the one or more blockchain can be satisfied, for example, as further described herein,regarding FIGS. 15-19.

It can be understood that data management component 2022 can compriseone or more of system components, and/or portions thereof, to facilitateany of the functionality described herein and/or ancillary thereto, suchas by execution of computer-executable instructions by a computer, aprocessor, etc. (e.g., one or more of host processors 2018, processor2204, etc.). Moreover, any of the components described herein (e.g.,data management component 2022, etc.) can be configured to perform thedescribed functionality (e.g., via computer-executable instructionsstored in a tangible computer readable medium, and/or executed by acomputer, a processor, etc.).

For still other non-limiting implementations, data safe or user datasafe 112 comprising device or system 2000, or portions thereof, can alsoinclude authorization component 2024 that can facilitate transmitting anauthorization (e.g., exemplary response 1202) to access personalinformation (PI), receive the request for authorization (e.g., exemplaryrequest 1104), and so on, for example, as further described herein,regarding FIGS. 5-19, for example, and/or other functionalitiesassociated with data safe or user data safe 112. Thus, as describedabove, an exemplary data safe or user data safe 112 comprising device orsystem 1100, or portions thereof, can include one or more hostprocessors 2018 that can be associated with authorization component 202to facilitate receiving, transmitting, authorizing access, etc.,regarding data and/or information (e.g., personal information (PI),supplemental information (SI), other authorization information (OAI),categories of use (CI), links or URIs, hashes (e.g., cryptographichashes), other information, digital signatures, offers, etc.), and/orinstructions for performing functions associated with and/or incident tothe disclosed subject matter as described herein, for example, regardingFIGS. 1-19, etc.

In a non-limiting embodiment, exemplary data safe or user data safe 112can comprise or be associated with a authorization component 2024configured to transmit an authorization (e.g., exemplary response 1202)to access a set of the number of block chains based on the determinedcategory of use (CI) associated with a request for authorization (e.g.,exemplary request 1104), for example, as further described herein,regarding FIGS. 5-14. In a further non-limiting example, exemplary datasafe or user data safe 112 can comprise or be associated with aauthorization component 2024 configured to receive the request forauthorization (e.g., exemplary request 1104), wherein the authorizationcomponent 2024 can be further configured to transmit the authorization(e.g., exemplary response 1202) comprising one or more cryptographichash associated with a last block (e.g., last or last subsequent block1002) of the one or more responsive block chain and a link to the lastblock (e.g., last or last subsequent block 1002) of the one or moreresponsive block chain stored in the DFS, for example, as furtherdescribed herein, regarding FIGS. 5-14. In still another non-limitingexample, exemplary data safe or user data safe 112 can comprise or beassociated with a authorization component 2024 configured to transmitthe one or more cryptographic hash associated with the last block (e.g.,last or last subsequent block 1002) of the one or more responsive blockchain and the link to the last block (e.g., last or last subsequentblock 1002) of the one or more responsive block chain stored in the DFSencrypted, for example, as further described herein, regarding FIGS.5-14.

In another non-limiting embodiment, exemplary data safe or user datasafe 112 can comprise or be associated with a authorization component2024 configured to transmit a request for authorization (e.g., exemplaryrequest 1104) to access personal information (PI) and the determinedcategory of use (CI) associated with the request for authorization(e.g., exemplary request 1104), wherein the authorization component 2024can be further configured to receive one or more cryptographic hashassociated with a last block (e.g., last or last subsequent block 1002)of one or more block chain and a link to the last block (e.g., last orlast subsequent block 1002) of the one or more block chain stored in adistributed file system (DFS), for example, as further described herein,regarding FIGS. 15-19. In a further non-limiting example, exemplary datasafe or user data safe 112 can comprise or be associated with aauthorization component 2024 configured to receive an encrypted responseand can be associated with a cryptographic component 2026 configured todecrypt the encrypted response comprising the last block (e.g., last orlast subsequent block 1002) of one or more block chain and the link tothe last block (e.g., last or last subsequent block 1002) of the one ormore block chain stored in a distributed file system, for example, asfurther described herein, regarding FIGS. 15-19. In yet anothernon-limiting example, exemplary data safe or user data safe 112 cancomprise or be associated with a authorization component 2024 configuredto transmit a follow-up request (e.g., exemplary request 1104) foradditional authorization (e.g., exemplary response 1202) to accesspersonal information (PI), for example, as further described herein,regarding FIGS. 15-19. In still another non-limiting example, exemplarydata safe or user data safe 112 can comprise or be associated with aauthorization component 2024 configured to transmit the follow-uprequest (e.g., exemplary request 1104) for additional authorization(e.g., exemplary response 1202) to access personal information (PI), forexample, as further described herein, regarding FIGS. 15-19.

It can be understood that authorization component 2024 can comprise oneor more of system components, and/or portions thereof, to facilitate anyof the functionality described herein and/or ancillary thereto, such asby execution of computer-executable instructions by a computer, aprocessor, etc. (e.g., one or more of host processors 2018, processor2204, etc.). Moreover, any of the components described herein (e.g.,authorization component 2024, etc.) can be configured to perform thedescribed functionality (e.g., via computer-executable instructionsstored in a tangible computer readable medium, and/or executed by acomputer, a processor, etc.).

For still other non-limiting implementations, data safe or user datasafe 112 comprising device or system 2000, or portions thereof, can alsoinclude cryptographic component 202 that can facilitateencryption/decryption, and the handling of information or data incidentthereto, for example, as further described herein, regarding FIGS. 5-19,for example, and/or other functionalities associated with data safe oruser data safe 112. Thus, as described above, an exemplary data safe oruser data safe 112 comprising device or system 1100, or portionsthereof, can include one or more host processors 2018 that can beassociated with cryptographic component 202 to facilitateencryption/decryption of data and/or information (e.g., personalinformation (PI), supplemental information (SI), other authorizationinformation (OAI), categories of use (CI), links or URIs, hashes (e.g.,cryptographic hashes), other information, digital signatures, offers,etc.), and/or instructions for performing functions associated withand/or incident to the disclosed subject matter as described herein, forexample, regarding FIGS. 1-19, etc.

Thus, cryptographic component 2026 can facilitate securing data and/orinformation being written to, stored in, and/or read from the storagecomponent 2020 (e.g., account and/or profile information, messages,queries, requests, responses, etc.), transmitted to and/or received froma connected network (e.g., such as for transmitting user 102 and/orassociated device information to a trusted intermediary, etc.), and/orcreating a secure communication channel as part of a secure associationof various devices with exemplary implementations of data safe or userdata safe 112 comprising non-limiting embodiments of devices or systems2000, or portions thereof, with a user 102 (or one or more of thirdparties, such as one or more data provider(s) 104, one or more datasource(s) 108, one or more verifying entities 110, etc.) facilitatingvarious aspects of the disclosed subject matter to ensure that protecteddata can only be accessed by those entities authorized and/orauthenticated to do so. To the same ends, cryptographic component 2026can also provide asymmetric cryptographic accelerators and tools (e.g.,RSA, Digital Signature Standard (DSS), and the like) in addition toaccelerators and tools (e.g., Secure Hash Algorithm (SHA) and itsvariants such as, for example, SHA-0, SHA-1, SHA-224, SHA-256, SHA-384,SHA-512, SHA-3, and so on). As described, any of the componentsdescribed herein (e.g., cryptographic component 2026, etc.) can beconfigured to perform the described functionality (e.g., viacomputer-executable instructions stored in a tangible computer readablemedium, and/or executed by a computer, a processor, etc.).

In a non-limiting embodiment, exemplary data safe or user data safe 112can comprise or be associated with a cryptographic component 2026configured to encrypt a number of a cryptographic hash of a prior block(e.g., immediately prior subsequent block 1004, root block 1006) ofpersonal information (PI) in the one or more block chain, a link to theprior block (e.g., immediately prior subsequent block 1004, root block1006) of personal information (PI) in the one or more block chain storedin the DFS, a verifying entity associated with the personal information(PI), a digital signature associated with the verifying entity,information associated with an encryption key or decryption key, orother authorization information (OAI) associated with the set of thenumber of block chains, for example, as further described herein,regarding FIGS. 5-19. In a further non-limiting example, exemplary datasafe or user data safe 112 can comprise or be associated with acryptographic component 2026 configured to decrypt the encryptedresponse (e.g., exemplary response 1202) comprising the last block(e.g., last or last subsequent block 1002) of one or more block chainand the link to the last block (e.g., last or last subsequent block1002) of the one or more block chain stored in a distributed filesystem, for example, as further described herein, regarding FIGS. 15-19.

It can be understood that cryptographic component 2026 can comprise oneor more of system components, and/or portions thereof, to facilitate anyof the functionality described herein and/or ancillary thereto, such asby execution of computer-executable instructions by a computer, aprocessor, etc. (e.g., one or more of host processors 2018, processor2204, etc.). Moreover, any of the components described herein (e.g.,cryptographic component 2026, etc.) can be configured to perform thedescribed functionality (e.g., via computer-executable instructionsstored in a tangible computer readable medium, and/or executed by acomputer, a processor, etc.).

For still other non-limiting implementations, data safe or user datasafe 112 comprising device or system 2000, or portions thereof, can alsoinclude contract management component 2028 that can facilitate automatedor self-executing contract execution based on personal information (PI)stored in one or more block chains based on one or more categories ofuse (CI) stored in DFS, for example, as further described herein,regarding FIGS. 5-19, for example, and/or other functionalitiesassociated with data safe or user data safe 112. Thus, as describedabove, an exemplary data safe or user data safe 112 comprising device orsystem 1100, or portions thereof, can include one or more hostprocessors 2018 that can be associated with contract managementcomponent 2028 to facilitate automated or self-executing contractexecution associated with data and/or information (e.g., personalinformation (PI), supplemental information (SI), other authorizationinformation (OAI), categories of use (CI), links or URIs, hashes (e.g.,cryptographic hashes), other information, digital signatures, offers,etc.), and/or instructions for performing functions associated withand/or incident to the disclosed subject matter as described herein, forexample, regarding FIGS. 1-19, etc.

In another non-limiting embodiment, exemplary data safe or user datasafe 112 can comprise or be associated with a contract managementcomponent 2028 configured to determine that the one or more block chaindoes not comprise one or more responsive block chain responsive to theoffer, and wherein the authorization component 2024 can be furtherconfigured to transmit a follow-up request (e.g., exemplary request1104) for additional authorization (e.g., exemplary response 1202) toaccess personal information (PI), for example, as further describedherein, regarding FIGS. 15-19. In a further non-limiting example,exemplary data safe or user data safe 112 can comprise or be associatedwith a contract management component 2028 configured to determine thatthe one or more block chain comprises the one or more responsive blockchain comprising personal information (PI) responsive to the offer, forexample, as further described herein, regarding FIGS. 15-19.

In another non-limiting example, exemplary data safe or user data safe112 can comprise or be associated with a contract management component2028 configured to determine based on the offer, a number of one or moredata requirements associated with personal information (PI), one or morecontract requirement associated with the offer, one or more successaction defined by the offer, or one or more failure action defined bythe offer, for example, as further described herein, regarding FIGS.15-19. In still another non-limiting example, exemplary data safe oruser data safe 112 can comprise or be associated with a contractmanagement component 2028 configured to execute, based on the offer, oneor more of the one or more success action defined by the offer or theone or more failure action defined by the offer, for example, as furtherdescribed herein, regarding FIGS. 15-19. In a further non-limitingexample, exemplary data safe or user data safe 112 can comprise or beassociated with a contract management component 2028 configured tocompare the one or more responsive block chain comprising personalinformation (PI) to information associated with the offer, for example,as further described herein, regarding FIGS. 15-19.

In further non-limiting examples, exemplary data safe or user data safe112 can comprise or be associated with a contract management component2028 configured to determine that one or more of the one or more datarequirement associated with personal information (PI) or the one or morecontract requirement associated with the offer can be not satisfied bythe one or more responsive block chain comprising personal information(PI), for example, as further described herein, regarding FIGS. 15-19.In still other non-limiting examples, exemplary data safe or user datasafe 112 can comprise or be associated with a contract managementcomponent 2028 configured to determine that the one or more datarequirement associated with personal information (PI) and the one ormore contract requirement associated with the offer are satisfied by theone or more responsive block chain comprising personal information (PI),for example, as further described herein, regarding FIGS. 15-19.

In further non-limiting examples, exemplary data safe or user data safe112 can comprise or be associated with a contract management component2028 configured to determine that one or more of personal information(PI) comprising personally identifying information or other personalinformation (PI) satisfies the one or more data requirement associatedwith personal information (PI), wherein the personally identifyinginformation can be defined as information or combinations of informationthat resolve to a unique user (e.g., user 102), meeting or exceeding apredetermined threshold confidence level, and wherein the other personalinformation (PI) can be defined as other information or combinations ofother information that does not resolve to the unique user (e.g., user102), by failing to meet or exceed the predetermined thresholdconfidence level, and wherein the one or more block chain can be basedon at least the personally identifying information, for example, asfurther described herein, regarding FIGS. 15-19.

In still further non-limiting examples, exemplary data safe or user datasafe 112 can comprise or be associated with a contract managementcomponent 2028 configured to execute the machine-executable codeassociated with the offer defined by the one or more limitationassociated with the other authorization information (OAI) comprising oneor more term of use associated with the personal information (PI),including one or more of an expiration term for one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), a validity term associated with the personalinformation (PI), one or more of a payee or a requested fee associatedwith the one or more of the authorization (e.g., exemplary response1202) or the personal information (PI), one or more of a transmissionlimit or a storage limit associated with the one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), or a restriction associated with the one or more ofthe authorization (e.g., exemplary response 1202) or the personalinformation (PI) on a third party (e.g., one or more of third parties,such as one or more data provider(s) 104, one or more data source(s)108, one or more verifying entities 110, one or more other dataconsumer(s) 106, etc.), for example, as further described herein,regarding FIGS. 15-19.

It can be understood that contract management component 2028 cancomprise one or more of system components, and/or portions thereof, tofacilitate any of the functionality described herein and/or ancillarythereto, such as by execution of computer-executable instructions by acomputer, a processor, etc. (e.g., one or more of host processors 2018,processor 2204, etc.). Moreover, any of the components described herein(e.g., contract management component 2028, etc.) can be configured toperform the described functionality (e.g., via computer-executableinstructions stored in a tangible computer readable medium, and/orexecuted by a computer, a processor, etc.).

Referring again to FIG. 20, data safe or user data safe 112 comprisingdevice or system 2000, or portions thereof, can also include systemmanagement layer 2016, which can be associated with one or more hostprocessors 2018, can facilitate various aspects of the disclosed subjectmatter, as described above. For instance, system management layer 2016can facilitate transmitting and/or receiving information and/or datathat can be written to, stored in, and/or read from the storagecomponent 2020, can facilitate transmitting and/or receiving informationand/or data between and/or among one or more of system components, asfurther described herein, and/or one or more components associated withuser interface component 2004, one or more communications components,and so on, and/or one or more host processors 2018, can facilitatecontrol and/or execution of one or more of system components, etc. As afurther non-limiting example, the system management layer 2016 canfacilitate transmitting data, information, and/or instructions betweenfront-end system 2002 and back-end system 2006, can facilitatetransmitting and/or receiving data, information, and/or instructionsincident to various aspects and/or functionalities associated with datasafe or user data safe 112, or otherwise, and the like, as further asdescribed herein, for example, regarding FIGS. 1-19, etc. In a furthernon-limiting example involving an exemplary implementation of data safeor user data safe 112 comprising system management layer 2016, orportions thereof, data safe or user data safe 112 can facilitatepresenting actionable options (e.g., via, in lieu of, in addition to,and/or complementary to user interface component 2004) to a user 102 (orone or more of third parties, such as one or more data provider(s) 104,one or more data source(s) 108, one or more verifying entities 110, oneor more other data consumer(s) 106, etc.), for example, by identifyingand/or determining options and/or activities available to user 102within data safe or user data safe 112, based in part on one or more ofwhether user 102 (or others) has installed an appropriately configuredapp on a device associated with user 102 (or others), whether user 102(or others) is registered and/or authenticated with data safe or userdata safe 112, or otherwise, capabilities of one or more systemcomponents, etc.

In yet another non-limiting example in the context of hybrid webapplications or “mashups,” system management layer 2016 can facilitateusing and/or combining data, information, and/or functionalityassociated with data safe or user data safe 112 (or components orportions thereof) with one or more other sources to create compoundapplications or services by providing one or more APIs associated withone or more system components, and by providing access to one or moreinformation and/or data sources associated with data safe or user datasafe 112. To these and related ends, further non-limitingimplementations of data safe or user data safe 112 comprising systemmanagement layer 2016 (or one or more system components), or portionsthereof, can provide one or more APIs that can expose data, information,and/or functionality associated with the one or more system components(e.g., one or more of host processor 2018, storage component 2020, datamanagement component 2022, authorization component 2024, cryptographiccomponent 2026, contract management component 2028, registration and/orauthentication component(s) (not shown), one or more profile managementcomponent(s) (not shown), one or more privacy and/or control component(not shown), one or more search component(s) (not shown), one or moreanalysis component(s) (not shown), one or more monetization component(s)(not shown), one or more marketing component(s) (not shown), etc.),either as described above, or as further described herein.

It should be noted that, as depicted in FIG. 20, devices or systems 2000are described as monolithic devices or systems. However, it is to beunderstood that the various components and/or the functionality providedthereby can be incorporated into one or more host processors 2018 orprovided by one or more other connected devices. Accordingly, it is tobe understood that more or less of the described functionality may beimplemented, combined, and/or distributed (e.g., among network devicesor systems, servers, databases, and the like), according to context,system design considerations, and/or marketing factors. Moreover, any ofthe components described herein can be configured to perform thedescribed functionality (e.g., via computer-executable instructionsstored in a tangible computer readable medium, and/or executed by acomputer, a processor, etc.).

Accordingly, non-limiting embodiments of exemplary devices or systems2000 can comprise or be associated with a processor and a memory thatstores computer executable components that, when executed by theprocessor, facilitate performance of operations, wherein the computerexecutable components can comprise a storage component 2020 configuredto store personal information (PI) associated with a user (e.g., user102) in a distributed file system (DFS), for example, as furtherdescribed herein, regarding FIGS. 5-14.

In a non-limiting aspect, exemplary storage component 2020 can befurther configured to store the personal information (PI) withsupplemental information (SI) encrypted to facilitate one or more ofcreation of one or more block chain of the number of block chains ordetermining an applicability status of the request for authorization(e.g., exemplary request 1104), for example, as further describedherein, regarding FIGS. 5-14. In a further non-limiting aspect,exemplary storage component 2020 can be further configured to store thepersonal information (PI) in the DFS comprising inter-planetary filesystem (IPFS), for example, as further described herein, regarding FIGS.5-14.

Still further non-limiting embodiments of exemplary devices or systems2000 can comprise or be associated with a data management component 2022configured to create a number of block chains of personal information(PI), based on a determined category of use (CI) of each of the numberof block chains, for example, as further described herein, regardingFIGS. 5-14. For instance, in a non-limiting aspect, exemplary datamanagement component 2022 can be associated with a cryptographiccomponent 2026 configured to encrypt a number of a cryptographic hash ofa prior block (e.g., immediately prior subsequent block 1004, root block1006) of personal information (PI) in the one or more block chain, alink to the prior block (e.g., immediately prior subsequent block 1004,root block 1006) of personal information (PI) in the one or more blockchain stored in the DFS, a verifying entity associated with the personalinformation (PI), a digital signature associated with the verifyingentity, information associated with an encryption key or decryption key,or other authorization information (OAI) associated with the set of thenumber of block chains, for example, as further described herein,regarding FIGS. 5-19.

For instance, an exemplary link to the prior block (e.g., immediatelyprior subsequent block 1004, root block 1006) of personal information(PI) in the one or more block chain can comprise an encrypted link tothe prior block (e.g., immediately prior subsequent block 1004, rootblock 1006) of personal information (PI) in the one or more block chain,for example, as further described herein, regarding FIGS. 5-14.

In another non-limiting aspect, exemplary data management component 2022can be further configured to determine the one or more term of use,comprising one or more of an expiration term for one or more of theauthorization or the personal information (PI), a validity termassociated with the personal information (PI), one or more of a payee ora requested fee associated with the one or more of the authorization orthe personal information (PI), one or more of a transmission limit or astorage limit associated with the one or more of the authorization orthe personal information (PI), or a restriction associated with the oneor more of the authorization or the personal information (PI) on a thirdparty (e.g., one or more of third parties, such as one or more dataprovider(s) 104, one or more data source(s) 108, one or more verifyingentities 110, one or more other data consumer(s) 106, etc.), forexample, as further described herein, regarding FIGS. 5-14.

In still another non-limiting aspect, exemplary data managementcomponent 2022 can be further configured to determine whether thepersonal information (PI) can be personally identifying information orother personal information (PI), wherein the personally identifyinginformation can be defined as information or combinations of informationthat resolve to a unique user (e.g., user 102), meeting or exceeding apredetermined threshold confidence level, and wherein the other personalinformation (PI) can be defined as other information or combinations ofother information that does not resolve to the unique user (e.g., user102), by failing to meet or exceed the predetermined thresholdconfidence level, and can be further configured to create the number ofblock chains based on at least the personally identifying information,for example, as further described herein, regarding FIGS. 5-14.

In yet another non-limiting aspect, exemplary data management component2022 can be further configured to determine from the request forauthorization (e.g., exemplary request 1104) the determined category ofuse (CI), wherein the data management component 2022, can be furtherconfigured to determine whether one or more responsive block chainexists that can be responsive to the determined category of use (CI) andthe request for authorization (e.g., exemplary request 1104) in the setof the number of block chains, wherein the data management component2022 can be further configured to create the one or more responsiveblock chain if the one or more responsive block chain does not exist,for example, as further described herein, regarding FIGS. 5-14.

In further non-limiting aspects, exemplary devices or systems 2000 cancomprise or be associated with an authorization component 2024configured to transmit an authorization (e.g., exemplary response 1202)to access a set of the number of block chains based on the determinedcategory of use (CI) associated with a request for authorization (e.g.,exemplary request 1104), for example, as further described herein,regarding FIGS. 5-14. For instance, exemplary other authorizationinformation (OAI) associated with the set of the number of block chainscan comprise one or more term of use determined by the user (e.g., user102), for example, as further described herein, regarding FIGS. 5-14. Ina further non-limiting aspect, exemplary authorization component 2024can be further configured to receive the request for authorization(e.g., exemplary request 1104), the authorization component 2024 can befurther configured to transmit the authorization (e.g., exemplaryresponse 1202) comprising one or more cryptographic hash associated witha last block (e.g., last or last subsequent block 1002) of the one ormore responsive block chain and a link to the last block (e.g., last orlast subsequent block 1002) of the one or more responsive block chainstored in the DFS, for example, as further described herein, regardingFIGS. 5-14. In still further non-limiting aspects, exemplaryauthorization component 2024 can be further configured to transmit theone or more cryptographic hash associated with the last block (e.g.,last or last subsequent block 1002) of the one or more responsive blockchain and the link to the last block (e.g., last or last subsequentblock 1002) of the one or more responsive block chain stored in the DFSencrypted, for example, as further described herein, regarding FIGS.5-14.

Further non-limiting embodiments of exemplary devices or systems 2000can comprise or be associated with a processor and a memory that storescomputer executable components that, when executed by the processor,facilitate performance of operations, wherein the computer executablecomponents can comprise a storage component 2020 configured to storemachine-executable code associated with an offer, wherein the offer canbe contingent upon access to personal information (PI) stored in a setof a number of block chains, wherein the number of block chains arebased on a determined category of use (CI) of personal information (PI)in each of the number of block chains, for example, as further describedherein, regarding FIGS. 15-19.

Still further non-limiting embodiments of exemplary devices or systems2000 can comprise or be associated with a data management component 2022configured to determine the determined category of use (CI) of personalinformation (PI), for example, as further described herein, regardingFIGS. 15-19.

In a non-limiting example, exemplary data management component 2022 canbe further configured to retrieve the last block (e.g., last or lastsubsequent block 1002) of the one or more block chain via link to thelast block (e.g., last or last subsequent block 1002) of the one or moreblock chain stored in the DFS and/or determine other authorizationinformation (OAI) associated with the one or more block chain, andwherein the data management component 2022 can be further configured toprocess the one or more block chain to determine personal information(PI), for example, as further described herein, regarding FIGS. 15-19.

In another non-limiting example, exemplary data management component2022 can be further configured to determine a number of a cryptographichash of a prior block (e.g., immediately prior subsequent block 1004,root block 1006) of personal information (PI) associated with the one ormore block chain, a link to the prior block (e.g., immediately priorsubsequent block 1004, root block 1006) of personal information (PI)associated with the one or more block chain stored in the DFS, averifying entity associated with the personal information (PI), adigital signature associated with the verifying entity, or informationassociated with an encryption key or decryption key, for example, asfurther described herein, regarding FIGS. 15-19.

In a non-limiting example, exemplary data management component 2022 canbe further configured to determine that one or more limitationassociated with the other authorization information (OAI) specified inthe one or more block chain can be satisfied, for example, as furtherdescribed herein, regarding FIGS. 15-19.

Further non-limiting embodiments of exemplary devices or systems 2000can comprise or be associated with a an authorization component 2024configured to transmit a request for authorization (e.g., exemplaryrequest 1104) to access personal information (PI) and the determinedcategory of use (CI) associated with the request for authorization(e.g., exemplary request 1104), wherein the authorization component 2024can be further configured to receive one or more cryptographic hashassociated with a last block (e.g., last or last subsequent block 1002)of one or more block chain and a link to the last block (e.g., last orlast subsequent block 1002) of the one or more block chain stored in adistributed file system (DFS), for example, as further described herein,regarding FIGS. 15-19. In a non-limiting aspect, exemplary authorizationcomponent 2024 can be further configured to receive an encryptedresponse (e.g., exemplary response 1202) and can be associated with acryptographic component 2026 configured to decrypt the encryptedresponse (e.g., exemplary response 1202) comprising the last block(e.g., last or last subsequent block 1002) of one or more block chainand the link to the last block (e.g., last or last subsequent block1002) of the one or more block chain stored in a distributed filesystem, for example, as further described herein, regarding FIGS. 5-19.In a further non-limiting aspect, exemplary authorization component 2024can be further configured to transmit a follow-up request (e.g.,exemplary request 1104) for additional authorization (e.g., exemplaryresponse 1202) to access personal information (PI), for example, asfurther described herein, regarding FIGS. 15-19. In another example,exemplary authorization component 2024 can be further configured totransmit the follow-up request (e.g., exemplary request 1104) foradditional authorization (e.g., exemplary response 1202) to accesspersonal information (PI), for example, as further described herein,regarding FIGS. 15-19.

Still further non-limiting embodiments of exemplary devices or systems2000 can comprise or be associated with a contract management component2028 configured to determine that the one or more block chain does notcomprise one or more responsive block chain responsive to the offer, forexample, as further described herein, regarding FIGS. 15-19. Forinstance, in a non-limiting aspect, exemplary contract managementcomponent 2028 can be further configured to determine that the one ormore block chain comprises the one or more responsive block chaincomprising personal information (PI) responsive to the offer, forexample, as further described herein, regarding FIGS. 15-19. In yetanother non-limiting aspect, exemplary contract management component2028 can be further configured to determine based on the offer, a numberof one or more data requirements associated with personal information(PI), one or more contract requirement associated with the offer, one ormore success action defined by the offer, or one or more failure actiondefined by the offer, for example, as further described herein,regarding FIGS. 15-19. In still another non-limiting aspect, exemplarycontract management component 2028 can be further configured to execute,based on the offer, one or more of the one or more success actiondefined by the offer or the one or more failure action defined by theoffer, for example, as further described herein, regarding FIGS. 15-19.

Further non-limiting embodiments can comprise or be associated with anexemplary contract management component 2028 that can be furtherconfigured to compare the one or more responsive block chain comprisingpersonal information (PI) to information associated with the offer, forexample, as further described herein, regarding FIGS. 15-19. In stillanother non-limiting aspect, exemplary contract management component2028 can be further configured to determine that one or more of the oneor more data requirement associated with personal information (PI) orthe one or more contract requirement associated with the offer can benot satisfied by the one or more responsive block chain comprisingpersonal information (PI), for example, as further described herein,regarding FIGS. 15-19. In addition, exemplary contract managementcomponent 2028 can be further configured to determine that the one ormore data requirement associated with personal information (PI) and theone or more contract requirement associated with the offer are satisfiedby the one or more responsive block chain comprising personalinformation (PI), for example, as further described herein, regardingFIGS. 15-19. In other non-limiting embodiments, exemplary contractmanagement component 2028 can be further configured to determine thatone or more of personal information (PI) comprising personallyidentifying information or other personal information (PI) satisfies theone or more data requirement associated with personal information (PI),wherein the personally identifying information can be defined asinformation or combinations of information that resolve to a unique user(e.g., user 102), meeting or exceeding a predetermined thresholdconfidence level, and wherein the other personal information (PI) can bedefined as other information or combinations of other information thatdoes not resolve to the unique user (e.g., user 102), by failing to meetor exceed the predetermined threshold confidence level, and wherein theone or more block chain can be based on at least the personallyidentifying information, for example, as further described herein,regarding FIGS. 15-19.

In still further non-limiting examples, exemplary contract managementcomponent 2028 can be further configured to execute themachine-executable code associated with the offer defined by the one ormore limitation associated with the other authorization information(OAI) comprising one or more term of use associated with the personalinformation (PI), including one or more of an expiration term for one ormore of the authorization (e.g., exemplary response 1202) or thepersonal information (PI), a validity term associated with the personalinformation (PI), one or more of a payee or a requested fee associatedwith the one or more of the authorization (e.g., exemplary response1202) or the personal information (PI), one or more of a transmissionlimit or a storage limit associated with the one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), or a restriction associated with the one or more ofthe authorization (e.g., exemplary response 1202) or the personalinformation (PI) on a third party (e.g., one or more of third parties,such as one or more data provider(s) 104, one or more data source(s)108, one or more verifying entities 110, one or more other dataconsumer(s) 106, etc.), for example, as further described herein,regarding FIGS. 15-19.

FIG. 21 illustrates an overview of an exemplary computing environment2100 suitable for incorporation of embodiments of the disclosed subjectmatter. For example, computing environment 2100 can comprise wiredcommunication environments, wireless communication environments, and soon. As a further example, computing environment 2100 can furthercomprise one or more of a wireless access component 2102, communicationsnetworks 2104, the Internet 2106, etc., with which a user 102 can employany of a variety of devices (e.g., device 2110, devices 2112-2120, andso on) comprising an appropriately configured application, or app 2108(e.g., such as via an app appropriately configured for a specific deviceassociated with user 102, such as described below with reference toFIGS. 22-23, and so on, etc.), or other functionality (e.g., browsers,clients, etc.) to communicate data and/or information over acommunication medium (e.g., a wired medium 2122, a wireless medium viawireless access component 2102, etc.) according to an agreed protocol,to facilitate communication of data and/or information associated withdata safe or user data safe 112 between and/or among one or more of datasafe or user data safe 112, user 102, one or more data consumer(s) 106,and/or other third parties and networks 2128 (e.g., one or more of thirdparties, such as one or more data provider(s) 104, one or more datasource(s) 108, one or more verifying entities 110, one or more otherdata consumer(s) 106, etc.), and/or computing systems or devicesassociated therewith, such as device 2110, computing systems or devices2124, 2126, and 2130, respectively (e.g., via an operating system,application software, device drivers, communications stacks, etc., whichcan perform such actions on behalf of such computing systems ordevices). For instance, user interface component 2006 can facilitateinteraction between a user 102 (e.g., via a device associated with user102, and so on, etc.), such as via a mobile device native app installeddirectly onto the device (e.g., smartphone, tablet, etc.) coded in itsown native program language, and/or via a mobile web app (e.g., anInternet-enabled app, etc.) that has specific functionality for mobiledevices and/or accessed through the mobile device's web browser, asdescribed herein.

Thus, as described herein, in various non-limiting aspects, devices 2110(e.g., comprising app 2108, or otherwise, and so on, etc.) employed inconnection with data safe or user data safe 112 or functionalitiesthereof can facilitate various actions described herein regarding FIGS.1-20, for example.

Accordingly, computing environment 2100 can comprise a number ofcomponents to facilitate described functionalities according to variousaspects of the disclosed subject matter, among other related functions.While various embodiments are described with respect to the componentsof computing environment 2100 and the further embodiments more fullydescribed herein, one having ordinary skill in the art would recognizethat various modifications could be made without departing from thespirit of the disclosed subject matter. Thus, it can be understood thatthe description herein is but one of many embodiments that may bepossible while keeping within the scope of the claims appended hereto.

Additionally, while device 2110 is shown as a generic network capabledevice, which can include any of a variety of devices (e.g., device2110, devices 2112-2120, and so on), device 2110 is intended to refer toa class of network capable devices that can one or more of receive,transmit, store, etc., data and or information incident to and that user102, data safe or user data safe 112, data consumer(s) 106, and/or thirdparties and networks 2128 (e.g., one or more of third parties, such asone or more data provider(s) 104, one or more data source(s) 108, one ormore verifying entities 110, one or more other data consumer(s) 106,etc.) can employ to facilitate various techniques of the disclosedsubject matter. However, the discussion of the foregoing distinction isintended for illustration and not limitation. While for purposes ofillustration, user 102 is described as performing certain actions, it isto be understood that device 2110 (e.g., via an operating system,application software, device drivers, communications stacks, etc.) canperform such actions on behalf of user 102, as further described herein.Similarly for third parties and networks 2128 (e.g., one or more ofthird parties, such as one or more data provider(s) 104, one or moredata source(s) 108, one or more verifying entities 110, one or moreother data consumer(s) 106, etc.), which can be discussed or describedas performing certain actions, it is to be understood that computingsystems or devices (e.g., 2126, 2130) associated with data consumer(s)106, and third parties and networks 2128, respectively (e.g., via anoperating system, application software, device drivers, communicationsstacks, etc.) can perform such actions on behalf of data consumer(s)106, third parties and networks 2128, respectively.

Accordingly, exemplary device 2110 can include, without limitation, acellular phone 2112, a laptop computer 2114, a tablet personal computer(PC) device 2116, and/or a personal digital assistant (PDA) 2118, orother mobile device, and so on connected to a network via accesscomponent 2102 or otherwise. As further examples, device 2110 caninclude such devices as a network capable camera 2120 and other suchdevices (not shown) as a pen computing device, wearable computingdevice, portable digital music player, home entertainment devices,network capable devices, appliances, kiosks, and sensors, and so on. Itis to be understood that device 2110 can comprise more or lessfunctionality than those exemplary devices described above as thecontext requires and as further described herein in connection withFIGS. 1-20, etc., for instance.

According to various embodiments of the disclosed subject matter, device2110 can connect to other devices to facilitate accomplishing variousfunctions as further described herein (e.g., storing personalinformation (PI) and/or creating personal information (PI) block chainsin DFS. In addition, device 2110 can connect via one or morecommunications networks 2104 to a wired network 2122 (e.g., directly,via the Internet 2106, or otherwise). Wired network 2122 (as well ascommunications network 2104) can comprise any number of computers,servers, intermediate network devices, and the like to facilitatevarious functions as further described herein. As a non-limitingexample, wired network 2122 can include and/or be associated withcomputing systems or devices 2126 (e.g., one or more appropriatelyconfigured computing devices associated with, operated by, or operatedon behalf of one or more data consumer(s), etc.) as described above,that facilitates providing access to data safe or user data safe 112 forone or more data consumer(s) 106 to enable various operations asdescribed herein. In other non-limiting implementations, data safe oruser data safe 112 can facilitate various interactions and/orfunctionality as described herein, regarding FIGS. 5-14, etc.

In a further non-limiting example, wired network 2122 can include and/orbe associated with computing systems or devices 2130 (e.g., one or moreappropriately configured computing devices associated with, operated by,or operated on behalf of third parties and networks 2128 (e.g., one ormore of third parties, such as one or more data provider(s) 104, one ormore data source(s) 108, one or more verifying entities 110, one or moreother data consumer(s) 106, etc.), etc.) as described above, thatfacilitates providing access to data safe or user data safe 112 forthird parties and networks 2128 to enable various operations asdescribed herein. In still other non-limiting implementations, data safeor user data safe 112 can facilitate various interactions and/orfunctionality as described herein, regarding FIGS. 15-19, etc.

Exemplary data safe or user data safe 112 can further include any numberof intermediaries acting on behalf of one or more of users 102, datasafe or user data safe 112, third parties and networks 2128, and so on,to facilitate various functions as further described herein. In afurther non-limiting example, an intermediary acting on behalf of datasafe or user data safe 112 could store and/or provide access to dataand/or information associated with data safe or user data safe 112, suchas via storage and/or retrieval of personal information (PI) stored inpersonal information (PI) block chains in DFS, to other computingsystems (e.g., CRM platforms, MIS platforms, e-commerce systems, socialmedia networks, news networks, search networks, etc.) and/or thirdparties, (e.g., individuals, political organizations, employmentagencies organizations, service providing organizations, etc.).Moreover, data safe or user data safe 112 can be further configured toperform any number of additional and/or complementary functions incidentto functionalities as described above, regarding FIGS. 2-10, forexample.

In addition, wired network 2122 or systems (or components) thereof canfacilitate performing ancillary functions to accomplish varioustechniques described herein. For example, computing systems or devices2126 (or 2130) associated with one or more data consumer(s) 106 (and/orthird parties and networks 2128) can provide functions that facilitateauthentication and/or authorization of one or more of users 102, one ormore data consumer(s) 106, one or more third parties and networks 2128,and/or others to data safe or user data safe 112, transmission of dataand/or information associated with data safe or user data safe 112(e.g., via an API, etc.) and/or other information associated withfacilitating the provision, collection, use, distribution, and so on, ofuser information about user 102, as well as the validation,verification, authentication, and proper protection and control of suchuser information about user 102 to ensure smooth, efficient, andcost-effective business processes, and therefore, in turn, attractiveprices on the offered goods and services, as described above.Accordingly, in various non-limiting embodiments of the disclosedsubject matter, computing environment 2100 can further compriseadditional network components (not shown). For example, systems,devices, and/or components can be relatively simplistic and/or lackingcertain features to facilitate various techniques of the disclosedsubject matter. Thus, particular aspects of the disclosed subject mattercan be facilitated by additional network components (not shown) incommunication with the devices and/or other components of computingenvironment 2100.

For instance, computing systems or devices 2126 associated with one ormore data consumer(s) 106 can be capable of performing a number offunctions as described above regarding data safe or user data safe 112,and/or computing systems or devices 2126 associated with one or moredata consumer(s) 106, and functionality described above regardingcomputing systems or devices 2126 associated with one or more dataconsumer(s) 106 can likewise be provided by other components or devicesassociated with wired network 2122 (e.g., data safe or user data safe112, computing systems or devices 2130 associated with third parties andnetworks 2128, and/or others, or portions thereof, etc.). For example,functionality associated with data safe or user data safe 112 forproviding one or more of analyses, inferences, or insights can beprovided by one or more computing systems (not shown) that can beconsidered ancillary to, but associated with data safe or user data safe112. In a further non-limiting example, functionality associated withdata safe or user data safe 112 for search, monetization, and so on,without limitation, can be provided by one or more computing systems(not shown) that can be considered ancillary to, but associated withdata safe or user data safe 112, computing systems or devices 2126associated with one or more data consumer(s) 106, computing systems ordevices 2128 associated with third parties and networks 2128, etc. As afurther example, data collected, transmitted, and/or received by astorage component 2020 can be stored in an associated database system(not shown), in addition to various associated systems that comprise anetwork (not shown) participating in a distributed file system (DFS),such as IPFS. As a further example, analyses and reporting functions,and/or other information associated with one or more of an analysiscomponent (not shown), marketing component (not shown), rewardscomponent (not shown), and so on, without limitation, can also beprovided by associated systems such as CRM platforms, MIS platforms,and/or the like associated with data safe or user data safe 112.

In addition, as previously described, one or more intermediaries (e.g.,any of a number of MIS providers, e-commerce solution providers, and soon, etc.) acting on behalf one or more of user 102, one or more dataconsumer(s) 106, third parties and networks 2128, can provide subsets offunctionality such as described above regarding data safe or user datasafe 112. In yet another example, while one or more data consumer(s) 106or computing systems or devices 2126 associated with one or more dataconsumer(s) 106 can be capable of facilitating functions as previouslydescribed, one or more data consumer(s) 106 or computing systems ordevices 2126 associated with one or more data consumer(s) 106 could alsobe functionally limited resulting in an inability to authenticate one ormore data consumer(s) 106 or verify that access is authorized (e.g.,verifying fulfillment of a specified authentication requirement) inembodiments that employ such techniques. Accordingly, computingenvironment 2100 can comprise such further components (not shown) (e.g.,authentication, authorization and accounting (AAA) servers, e-commerceservers, database servers, application servers, etc.) in communicationwith one or more of data safe or user data safe 112, computing systemsor devices 2126 associated with one or more data consumer(s) 106,computing systems or devices 2128 associated with third parties andnetworks 2128, and/or user 102 to accomplish the desired functions,without limitation.

FIG. 22 depicts an exemplary non-limiting device or system suitable forperforming various aspects of the disclosed subject matter. For example,FIG. 22 depicts an exemplary non-limiting device or system 2200 suitablefor performing various aspects of the disclosed subject matter. Thedevice or system 2200 can be a stand-alone device or a portion thereof,a specially programmed computing device or a portion thereof (e.g., amemory retaining instructions for performing the techniques as describedherein coupled to a processor), and/or a composite device or systemcomprising one or more cooperating components distributed among severaldevices, as further described herein. As an example, exemplarynon-limiting device or system 2200 can comprise exemplary devices and/orsystems described above regarding FIGS. 1-20, or as further describedbelow regarding FIGS. 23-26, for example, or portions or combinationsthereof.

Accordingly, device or system 2200 can include a memory 2202 thatretains various instructions with respect to facilitating variousoperations, for example, such as: storing (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) personal information (PI)associated with a user (e.g., user 102) in a distributed file system(DFS); creating (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) a number of block chains of personal information (PI),based on a determined category of use (CI) of each of the number ofblock chains; transmitting (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) an authorization (e.g., exemplary response 1202)to access a set of the number of block chains based on the determinedcategory of use (CI) associated with a request for authorization (e.g.,exemplary request 1104); storing (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) the personal information (PI) ininter-planetary file system (IPFS); encrypting (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) a number of acryptographic hash of a prior block (e.g., immediately prior subsequentblock 1004, root block 1006) of personal information (PI) in the one ormore block chain, a link to the prior block (e.g., immediately priorsubsequent block 1004, root block 1006) of personal information (PI) inthe one or more block chain stored in the DFS, a verifying entityassociated with the personal information (PI), a digital signatureassociated with the verifying entity, information associated with anencryption key or decryption key, or other authorization information(OAI) associated with the set of the number of block chains; encrypting(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.)the personal information (PI) with supplemental information (SI) tofacilitate one or more of creation of one or more block chain of thenumber of block chains or determining an applicability status of therequest for authorization (e.g., exemplary request 1104); encrypting(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.) anencrypted link to the prior block (e.g., immediately prior subsequentblock 1004, root block 1006) of personal information (PI) in the one ormore block chain; encrypting (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) one or more term of use determined by theuser (e.g., user 102); determining (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) the one or more term of use,comprising one or more of an expiration term for one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), a validity term associated with the personalinformation (PI), one or more of a payee or a requested fee associatedwith the one or more of the authorization (e.g., exemplary response1202) or the personal information (PI), one or more of a transmissionlimit or a storage limit associated with the one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), or a restriction associated with the one or more ofthe authorization (e.g., exemplary response 1202) or the personalinformation (PI) on a third party; determining (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) the one or more term ofuse, comprising one or more of an expiration term for one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), a validity term associated with the personalinformation (PI), one or more of a payee or a requested fee associatedwith the one or more of the authorization (e.g., exemplary response1202) or the personal information (PI), one or more of a transmissionlimit or a storage limit associated with the one or more of theauthorization (e.g., exemplary response 1202) or the personalinformation (PI), or a restriction associated with the one or more ofthe authorization (e.g., exemplary response 1202) or the personalinformation (PI) on a third party; determining (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) whether the personalinformation (PI) is personally identifying information or other personalinformation (PI), wherein the personally identifying information isdefined as information or combinations of information that resolve to aunique user (e.g., user 102), meeting or exceeding a predeterminedthreshold confidence level, and wherein the other personal information(PI) is defined as other information or combinations of otherinformation that does not resolve to the unique user (e.g., user 102),by failing to meet or exceed the predetermined threshold confidencelevel, and creating the number of block chains based on at least thepersonally identifying information; and so on, as further describedherein, regarding FIGS. 5-14.

In other non-limiting implementations, device or system 2200 can includea memory 2202 that retains various instructions with respect tofacilitating various operations, for example, such as: receiving (e.g.,via device or system 2000, 2200, 2300, portions thereof, etc.) therequest for authorization (e.g., exemplary request 1104); determining(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.)from the request for authorization (e.g., exemplary request 1104) thedetermined category of use (CI); determining (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) whether one or more responsiveblock chain exists that is responsive to the determined category of use(CI) and the request for authorization (e.g., exemplary request 1104) inthe set of the number of block chains; creating (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) the one or moreresponsive block chain if the one or more responsive block chain doesnot exist; transmitting the authorization (e.g., exemplary response1202) comprising transmitting (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) one or more cryptographic hash associatedwith a last block (e.g., last or last subsequent block 1002) of the oneor more responsive block chain and a link to the last block (e.g., lastor last subsequent block 1002) of the one or more responsive block chainstored in the DFS; encrypting (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) the one or more cryptographic hashassociated with the last block (e.g., last or last subsequent block1002) of the one or more responsive block chain and the link to the lastblock (e.g., last or last subsequent block 1002) of the one or moreresponsive block chain with a requester encryption key; and so on, asfurther described herein, regarding FIGS. 5-14.

In other non-limiting implementations, device or system 2200 can includea memory 2202 that retains various instructions with respect tofacilitating various operations, for example, such as: storing (e.g.,via device or system 2000, 2200, 2300, portions thereof, etc.)machine-executable code associated with an offer, wherein the offer iscontingent upon access to personal information (PI) stored in a set of anumber of block chains, wherein the number of block chains are based ona determined category of use (CI) of personal information (PI) in eachof the number of block chains; determining (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) the determined category of use(CI) of personal information (PI); transmitting a request forauthorization (e.g., exemplary request 1104) to access personalinformation (PI) and the determined category of use (CI) associated withthe request for authorization (e.g., exemplary request 1104); receiving(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.)one or more cryptographic hash associated with a last block (e.g., lastor last subsequent block 1002) of one or more block chain and a link tothe last block (e.g., last or last subsequent block 1002) of the one ormore block chain stored in a distributed file system (DFS); receiving(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.) anencrypted response and decrypting (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) the encrypted response comprisingthe last block (e.g., last or last subsequent block 1002) of one or moreblock chain and the link to the last block (e.g., last or lastsubsequent block 1002) of the one or more block chain stored in adistributed file system; determining (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) that the one or more block chaindoes not comprise one or more responsive block chain responsive to theoffer; transmitting (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) a follow-up request (e.g., exemplary request1104) for additional authorization to access personal information (PI);determining (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) that the one or more block chain comprises the one ormore responsive block chain comprising personal information (PI)responsive to the offer; determining (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) based on the offer, a number of oneor more data requirements associated with personal information (PI), oneor more contract requirement associated with the offer, one or moresuccess action defined by the offer, or one or more failure actiondefined by the offer; and so on, as further described herein, regardingFIGS. 5-19.

In other non-limiting implementations, device or system 2200 can includea memory 2202 that retains various instructions with respect tofacilitating various operations, for example, such as: executing (e.g.,via device or system 2000, 2200, 2300, portions thereof, etc.) based onthe offer, one or more of the one or more success action defined by theoffer or the one or more failure action defined by the offer; comparing(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.)the one or more responsive block chain comprising personal information(PI) to information associated with the offer; determining (e.g., viadevice or system 2000, 2200, 2300, portions thereof, etc.) that one ormore of the one or more data requirement associated with personalinformation (PI) or the one or more contract requirement associated withthe offer is not satisfied by the one or more responsive block chaincomprising personal information (PI); transmitting (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) the follow-up request(e.g., exemplary request 1104) for additional authorization to accesspersonal information (PI); determining (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) that the one or more datarequirement associated with personal information (PI) and the one ormore contract requirement associated with the offer are satisfied by theone or more responsive block chain comprising personal information (PI);determining (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) that one or more of personal information (PI) comprisingpersonally identifying information or other personal information (PI)satisfies the one or more data requirement associated with personalinformation (PI), wherein the personally identifying information isdefined as information or combinations of information that resolve to aunique user (e.g., user 102), meeting or exceeding a predeterminedthreshold confidence level, and wherein the other personal information(PI) is defined as other information or combinations of otherinformation that does not resolve to the unique user (e.g., user 102),by failing to meet or exceed the predetermined threshold confidencelevel, and wherein the one or more block chain is based on at least thepersonally identifying information; retrieving (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) the last block (e.g.,last or last subsequent block 1002) of the one or more block chain vialink to the last block (e.g., last or last subsequent block 1002) of theone or more block chain stored in the DFS; determining (e.g., via deviceor system 2000, 2200, 2300, portions thereof, etc.) other authorizationinformation (OAI) associated with the one or more block chain;processing (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) the one or more block chain to determine personalinformation (PI); and so on, as further described herein, regardingFIGS. 5-19.

In still further non-limiting implementations, device or system 2200 caninclude a memory 2202 that retains various instructions with respect tofacilitating various operations, for example, such as: determining(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.) anumber of a cryptographic hash of a prior block (e.g., immediately priorsubsequent block 1004, root block 1006) of personal information (PI)associated with the one or more block chain, a link to the prior block(e.g., immediately prior subsequent block 1004, root block 1006) ofpersonal information (PI) associated with the one or more block chainstored in the DFS, a verifying entity associated with the personalinformation (PI), a digital signature associated with the verifyingentity, or information associated with an encryption key or decryptionkey; determining (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) that one or more limitation associated with the otherauthorization information (OAI) specified in the one or more block chainis satisfied; executing (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) machine-executable code associated with theoffer and defined by the one or more limitation associated with theother authorization information (OAI) comprising one or more term of useassociated with the personal information (PI), including one or more ofan expiration term for one or more of the authorization or the personalinformation (PI), a validity term associated with the personalinformation (PI), one or more of a payee or a requested fee associatedwith the one or more of the authorization or the personal information(PI), one or more of a transmission limit or a storage limit associatedwith the one or more of the authorization or the personal information(PI), or a restriction associated with the one or more of theauthorization or the personal information (PI) on a third party; and soon, as further described herein, regarding FIGS. 5-19.

The above example instructions and other suitable instructions forfunctionalities as described herein for example, regarding FIGS. 1-21,etc., can be retained within memory 2202, and a processor 2204 can beutilized in connection with executing the instructions.

FIG. 23 illustrates an exemplary non-limiting system or device 2300suitable for performing various aspects of the disclosed subject matter.As an illustrative example, exemplary non-limiting device or system 2300can comprise exemplary devices or systems of FIGS. 1-22, as describedabove, or portions thereof. System or device 2300 can comprise an inputcomponent 2302 that can receive data or signals, and performs typicalactions thereon (e.g., transmits to storage component 2308) the receiveddata or signal. A storage component 2308 can store the received data orsignal, as described above, for example, regarding storage component2020, memory 2202, etc., for subsequent processing or can provide it toa API component 2306, or a processor (e.g., one or more host processors2018, 2204, etc.), via a memory (e.g., memory 2202, etc.) over asuitable communications bus or otherwise, or to the output component2304.

Processor 2204 can be a processor dedicated to analyzing and performingfunctions on information received by input component 2302 and/orgenerating information for transmission by an output component 2304.Processor 2204 can be a processor that controls one or more portions ofsystem or device 2300, and/or a processor that analyzes informationreceived by input component 2302, generates information for transmissionby output component 2304, and performs various functionalitiesassociated API component 2306. API component 2306 can include variousalgorithms and routines to facilitate communication according specifiednetwork protocols and coding algorithms.

While API component 2306 is shown external to the Processor 2204 andmemory 2202, it is to be understood that API component 2306 can includecode or instructions stored in storage component 2308, storage component2020, memory 2202, etc., and/or subsequently retained in memory 2202 forexecution by Processor 2204. It can be understood that various routinesperformed by system or device 2300 can utilize artificial intelligencebased methods in connection with performing inference and/orprobabilistic determinations and/or statistical-based determinations inconnection with various aspects of the disclosed subject matter.

System or device 2300 can additionally comprise a memory (e.g., memory2202, etc.) that is operatively coupled to Processor 2204 and thatstores information such as described above, parameters, information, andthe like, wherein such information can be employed in connection withimplementing various aspects as described herein. memory 2202 canadditionally store received data and/or information (e.g., data and/orinformation associated with data safe or user data safe 112, etc.), aswell as software routines and/or instructions for functionality asdescribed above in reference to FIGS. 1-20, etc., for example.

As an illustration of a non-limiting implementation of the disclosedsubject matter, an exemplary system or device 2300 can be configured oradapted to provide various functionality characterized by a deviceassociated with user 102 (e.g., device 2110, etc.). For example, FIG. 21describes device 2110, associated with user 102, which can comprise anappropriately configured application, or app (e.g., appropriatelyconfigured for a specific device, etc.), such as app 2108.

Referring again to FIG. 23, an exemplary system or device 2300 cancomprise means for storing (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) personal information (PI) associated with a user(e.g., user 102) in a distributed file system (DFS), means for creating(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.) anumber of block chains of personal information (PI), based on adetermined category of use (CI) of each of the number of block chains,and means for transmitting (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) an authorization (e.g., exemplary response 1202to access a set of the number of block chains based on the determinedcategory of use (CI) associated with a request for authorization (e.g.,exemplary request 1104), as further described herein, for example,regarding FIGS. 5-20.

For instance, in a non-limiting aspect, exemplary means for storing thepersonal information (PI) can be associated with means for encrypting(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.)the personal information (PI) with supplemental information (SI) tofacilitate one or more of creation of one or more block chain of thenumber of block chains or determining an applicability status of therequest for authorization (e.g., exemplary request 1104), as furtherdescribed herein, for example, regarding FIGS. 5-20. In a furthernon-limiting aspect, exemplary means for storing the personalinformation (PI) in DFS can comprise means for storing (e.g., via deviceor system 2000, 2200, 2300, portions thereof, etc.) the personalinformation (PI) in inter-planetary file system (IPFS), as furtherdescribed herein, for example, regarding FIGS. 5-20.

In yet another non-limiting aspect, exemplary means for encrypting thepersonal information (PI) with supplemental information (SI) cancomprise means for encrypting (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) a number of a cryptographic hash of aprior block (e.g., immediately prior subsequent block 1004, root block1006) of personal information (PI) in the one or more block chain, alink to the prior block (e.g., immediately prior subsequent block 1004,root block 1006) of personal information (PI) in the one or more blockchain stored in the DFS, a verifying entity associated with the personalinformation (PI), a digital signature associated with the verifyingentity, information associated with an encryption key or decryption key,or other authorization information (OAI) associated with the set of thenumber of block chains, as further described herein, for example,regarding FIGS. 5-20. For instance, in a non-limiting aspect, exemplarymeans for encrypting the link to the prior block (e.g., immediatelyprior subsequent block 1004, root block 1006) of personal information(PI) in the one or more block chain can comprise means for encrypting(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.) anencrypted link to the prior block (e.g., immediately prior subsequentblock 1004, root block 1006) of personal information (PI) in the one ormore block chain, as further described herein, for example, regardingFIGS. 5-20. In a further non-limiting aspect, exemplary means forencrypting the link to the prior block (e.g., immediately priorsubsequent block 1004, root block 1006) of personal information (PI) inthe one or more block chain can comprise means for encrypting (e.g., viadevice or system 2000, 2200, 2300, portions thereof, etc.) an encryptedlink to the prior block (e.g., immediately prior subsequent block 1004,root block 1006) of personal information (PI) in the one or more blockchain, as further described herein, for example, regarding FIGS. 5-20.As a non-limiting example, exemplary means for encrypting the otherauthorization information (OAI) associated with the set of the number ofblock chains can comprise means for encrypting (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) one or more term of usedetermined by the user (e.g., user 102), in another non-limiting aspectas further described herein, for example, regarding FIGS. 5-20.

In further non-limiting implementations, exemplary system or device 2300can also comprise means for determining (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) the one or more term of use,comprising one or more of an expiration term for one or more of theauthorization (e.g., exemplary response 1202 or the personal information(PI), a validity term associated with the personal information (PI), oneor more of a payee or a requested fee associated with the one or more ofthe authorization (e.g., exemplary response 1202 or the personalinformation (PI), one or more of a transmission limit or a storage limitassociated with the one or more of the authorization (e.g., exemplaryresponse 1202 or the personal information (PI), or a restrictionassociated with the one or more of the authorization (e.g., exemplaryresponse 1202 or the personal information (PI) on a third party, asfurther described herein, for example, regarding FIGS. 5-20. Inaddition, in another non-limiting aspect, exemplary means for creatingthe number of block chains of personal information (PI) can comprisemeans for determining (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) whether the personal information (PI) can bepersonally identifying information or other personal information (PI),wherein the personally identifying information can be defined asinformation or combinations of information that resolve to a unique user(e.g., user 102), meeting or exceeding a predetermined thresholdconfidence level, and wherein the other personal information (PI) can bedefined as other information or combinations of other information thatdoes not resolve to the unique user (e.g., user 102), by failing to meetor exceed the predetermined threshold confidence level, and means forcreating the number of block chains based on at least the personallyidentifying information, as further described herein, for example,regarding FIGS. 5-20.

In further non-limiting implementations, exemplary system or device 2300can also comprise means for receiving (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) the request for authorization (e.g.,exemplary request 1104), means for determining (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) from the request forauthorization (e.g., exemplary request 1104) the determined category ofuse (CI), means for determining (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) whether one or more responsive block chainexists that can be responsive to the determined category of use (CI) andthe request for authorization (e.g., exemplary request 1104) in the setof the number of block chains, means for creating (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) the one or moreresponsive block chain if the one or more responsive block chain doesnot exist, and means for transmitting the authorization (e.g., exemplaryresponse 1202 can comprise means for transmitting (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) one or morecryptographic hash associated with a last block (e.g., last or lastsubsequent block 1002) of the one or more responsive block chain and alink to the last block (e.g., last or last subsequent block 1002) of theone or more responsive block chain stored in the DFS, as furtherdescribed herein, for example, regarding FIGS. 5-20.

For instance, in a non-limiting aspect, exemplary means for transmittingthe one or more cryptographic hash associated with the last block (e.g.,last or last subsequent block 1002) of the one or more responsive blockchain and the link to the last block (e.g., last or last subsequentblock 1002) of the one or more responsive block chain stored in the DFScan be associated with means for encrypting (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) the one or more cryptographichash associated with the last block (e.g., last or last subsequent block1002) of the one or more responsive block chain and the link to the lastblock (e.g., last or last subsequent block 1002) of the one or moreresponsive block chain with a requester encryption key, as furtherdescribed herein, for example, regarding FIGS. 5-20.

It can be appreciated that exemplary system or device 2300 can beconfigured and/or adapted in a similar fashion to provide various otherfunctionalities as described herein.

In further non-limiting implementations, exemplary system or device 2300can also comprise means for storing (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) machine-executable code associatedwith an offer, wherein the offer can be contingent upon access topersonal information (PI) stored in a set of a number of block chains,wherein the number of block chains are based on a determined category ofuse (CI) of personal information (PI) in each of the number of blockchains, means for determining (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) the determined category of use (CI) ofpersonal information (PI), means for transmitting a request forauthorization (e.g., exemplary request 1104) to access personalinformation (PI) and the determined category of use (CI) associated withthe request for authorization (e.g., exemplary request 1104), and meansfor receiving (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) one or more cryptographic hash associated with a lastblock (e.g., last or last subsequent block 1002) of one or more blockchain and a link to the last block (e.g., last or last subsequent block1002) of the one or more block chain stored in a distributed file system(DFS), as further described herein, for example, regarding FIGS. 5-20.

For instance, in a non-limiting aspect, exemplary means for receivingcan comprise means for receiving (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) an encrypted response and decrypting(e.g., via device or system 2000, 2200, 2300, portions thereof, etc.)the encrypted response comprising the last block (e.g., last or lastsubsequent block 1002) of one or more block chain and the link to thelast block (e.g., last or last subsequent block 1002) of the one or moreblock chain stored in a distributed file system, as further describedherein, for example, regarding FIGS. 5-20.

In yet another non-limiting implementation, exemplary system or device2300 can comprise means for determining (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) that the one or more blockchain does not comprise one or more responsive block chain responsive tothe offer and means for transmitting (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) a follow-up request (e.g., exemplaryrequest 1104) for additional authorization (e.g., exemplary response1202) to access personal information (PI), as further described herein,for example, regarding FIGS. 5-20.

In still another non-limiting implementation, exemplary system or device2300 can comprise means for determining (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) that the one or more blockchain can comprise the one or more responsive block chain comprisingpersonal information (PI) responsive to the offer, as further describedherein, for example, regarding FIGS. 5-20. For instance, in anothernon-limiting implementation, exemplary system or device 2300 cancomprise means for determining (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) based on the offer, a number of one ormore data requirements associated with personal information (PI), one ormore contract requirement associated with the offer, one or more successaction defined by the offer, or one or more failure action defined bythe offer, as further described herein, for example, regarding FIGS.5-20. In addition, in another non-limiting implementation, exemplarysystem or device 2300 can comprise means for executing (e.g., via deviceor system 2000, 2200, 2300, portions thereof, etc.) based on the offer,one or more of the one or more success action defined by the offer orthe one or more failure action defined by the offer, as furtherdescribed herein, for example, regarding FIGS. 5-20.

In yet another non-limiting implementation, exemplary system or device2300 can comprise means for comparing (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) the one or more responsive blockchain comprising personal information (PI) to information associatedwith the offer, as further described herein, for example, regardingFIGS. 5-20.

In a further non-limiting implementation, exemplary system or device2300 can comprise means for determining (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) that one or more of the one ormore data requirement associated with personal information (PI) or theone or more contract requirement associated with the offer can be notsatisfied by the one or more responsive block chain comprising personalinformation (PI), and means for transmitting (e.g., via device or system2000, 2200, 2300, portions thereof, etc.) the follow-up request foradditional authorization to access personal information (PI), as furtherdescribed herein, for example, regarding FIGS. 5-20. For example, inanother non-limiting implementation, exemplary system or device 2300 cancomprise means for determining (e.g., via device or system 2000, 2200,2300, portions thereof, etc.) that the one or more data requirementassociated with personal information (PI) and the one or more contractrequirement associated with the offer are satisfied by the one or moreresponsive block chain comprising personal information (PI), as furtherdescribed herein, for example, regarding FIGS. 5-20. For instance,exemplary means for determining that the one or more data requirementassociated with personal information (PI) can be satisfied can comprisemeans for determining (e.g., via device or system 2000, 2200, 2300,portions thereof, etc.) that one or more of personal information (PI)comprising personally identifying information or other personalinformation (PI) satisfies the one or more data requirement associatedwith personal information (PI), wherein the personally identifyinginformation can be defined as information or combinations of informationthat resolve to a unique user (e.g., user 102), meeting or exceeding apredetermined threshold confidence level, and wherein the other personalinformation (PI) can be defined as other information or combinations ofother information that does not resolve to the unique user (e.g., user102), by failing to meet or exceed the predetermined thresholdconfidence level, and wherein the one or more block chain can be basedon at least the personally identifying information, as further describedherein, for example, regarding FIGS. 5-20.

In yet another non-limiting implementation, exemplary system or device2300 can comprise means for retrieving (e.g., via device or system 2000,2200, 2300, portions thereof, etc.) the last block (e.g., last or lastsubsequent block 1002) of the one or more block chain via link to thelast block (e.g., last or last subsequent block 1002) of the one or moreblock chain stored in the DFS, means for determining (e.g., via deviceor system 2000, 2200, 2300, portions thereof, etc.) other authorizationinformation (OAI) associated with the one or more block chain, and meansfor processing (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) the one or more block chain to determine personalinformation (PI), wherein exemplary means for processing the one or moreblock chain to determine personal information (PI) can comprise meansfor determining (e.g., via device or system 2000, 2200, 2300, portionsthereof, etc.) a number of a cryptographic hash of a prior block (e.g.,immediately prior subsequent block 1004, root block 1006) of personalinformation (PI) associated with the one or more block chain, a link tothe prior block (e.g., immediately prior subsequent block 1004, rootblock 1006) of personal information (PI) associated with the one or moreblock chain stored in the DFS, a verifying entity associated with thepersonal information (PI), a digital signature associated with theverifying entity, or information associated with an encryption key ordecryption key, as further described herein, for example, regardingFIGS. 5-20.

In still further non-limiting implementations, exemplary system ordevice 2300 can comprise means for determining (e.g., via device orsystem 2000, 2200, 2300, portions thereof, etc.) that one or morelimitation associated with the other authorization information (OAI)specified in the one or more block chain can be satisfied, as furtherdescribed herein, for example, regarding FIGS. 5-20. For instance, in anon-limiting aspect, exemplary means for determining that the one ormore limitation associated with the other authorization information(OAI) specified can be satisfied can comprise means for executing (e.g.,via device or system 2000, 2200, 2300, portions thereof, etc.)machine-executable code associated with the offer and defined by the oneor more limitation associated with the other authorization information(OAI) comprising one or more term of use associated with the personalinformation (PI), including one or more of an expiration term for one ormore of the authorization or the personal information (PI), a validityterm associated with the personal information (PI), one or more of apayee or a requested fee associated with the one or more of theauthorization or the personal information (PI), one or more of atransmission limit or a storage limit associated with the one or more ofthe authorization (e.g., exemplary response 1202 or the personalinformation (PI), or a restriction associated with the one or more ofthe authorization (e.g., exemplary response 1202 or the personalinformation (PI) on a third party, as further described herein, forexample, regarding FIGS. 5-20.

It can be appreciated that exemplary system or device 2300 can beconfigured and/or adapted in a similar fashion to provide various otherfunctionalities as described herein.

It will be understood that storage component 2308, storage component2020, memory 2202, and/or any combination thereof as described hereincan be either volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory. By way of illustration, and notlimitation, nonvolatile memory can include read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as cache memory. By wayof illustration and not limitation, RAM is available in many forms suchas synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM),double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SynchlinkDRAM (SLDRAM), and direct Rambus RAM (DRRAM). The memory 2202 isintended to comprise, without being limited to, these and/or any othersuitable types of memory, including processor registers and the like. Inaddition, by way of illustration and not limitation, storage component2308 and/or storage component 2020, can include conventional storagemedia as in known in the art (e.g., hard disk drive, solid state disk(SSD), etc.).

It can be understood that various techniques described herein may beimplemented in connection with hardware or software or, whereappropriate, with a combination of both. As used herein, the terms“device,” “component,” “system” and the like are likewise intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution. For example,a “device,” “component,” subcomponent, “system” portions thereof, and soon, may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on computer and the computer can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers.

It can be further understood that while a brief overview of exemplarysystems, methods, scenarios, and/or devices has been provided, thedisclosed subject matter is not so limited. Thus, it can be furtherunderstood that various modifications, alterations, addition, and/ordeletions can be made without departing from the scope of theembodiments as described herein. Accordingly, similar non-limitingimplementations can be used or modifications and additions can be madeto the described embodiments for performing the same or equivalentfunction of the corresponding embodiments without deviating therefrom.

As described above, regarding FIGS. 1-20, etc., for example, inexemplary implementations of the disclosed subject matter, a userinterface such as a GUI can be provided, for example to facilitateinteractions with data safe or user data safe 112 according to variousaspects of the disclosed subject matter, among other related functions.In addition, additional embodiments of the disclosed subject matter canprovide computer-executable components that can be stored on a tangiblecomputer readable storage medium (e.g., storage component 2020, storagecomponent 2308, memory 2202, etc.), and that, in response to executionby a computing device (e.g., one or more of host processors 2018,processor 2204, etc.), can cause the computing device to displayinformation (e.g., on the computing device, on a remote computing deviceover a network, etc), for example, such as via a GUI.

For example, FIG. 23 illustrates an exemplary non-limiting block diagramdepicting tangible computer readable storage medium, such as storagecomponent 2308 (e.g., storage component 2020, etc.), that can comprisecomputer-executable components and that, in response to execution by acomputing device (e.g., one or more of host processors 1010, processor1204, etc.), can cause the computing device to display information(e.g., on the computing device, on a remote computing device over anetwork, etc). As a non-limiting example, the computer-executablecomponents of the tangible computer readable storage medium can comprisean appropriately configured application, or app, (e.g., appropriatelyconfigured for a specific device, etc.) such as described above for app2108 in FIG. 21, for instance. In another non-limiting example, thecomputer-executable components of the tangible computer readable storagemedium can comprise any of the components (e.g., communicationcomponents, user interface component 2004, system management layer 2016,and/or portions thereof, etc.) described herein regarding FIGS. 1-20,for instance. In any event, the computer-executable components of thetangible computer readable storage medium can provide a user interfaceto facilitate interactions with data safe or user data safe 112, asdescribed herein.

Exemplary Networked and Distributed Environments

One of ordinary skill in the art can appreciate that the variousembodiments of the disclosed subject matter and related systems,devices, and/or methods described herein can be implemented inconnection with any computer or other client or server device, which canbe deployed as part of a communications system, a computer network,and/or in a distributed computing environment, and can be connected toany kind of data store. In this regard, the various embodimentsdescribed herein can be implemented in any computer system orenvironment having any number of memory or storage units, and any numberof applications and processes occurring across any number of storageunits or volumes, which may be used in connection with communicationsystems using the techniques, systems, and methods in accordance withthe disclosed subject matter. The disclosed subject matter can apply toan environment with server computers and client computers deployed in anetwork environment or a distributed computing environment, havingremote or local storage. The disclosed subject matter can also beapplied to standalone computing devices, having programming languagefunctionality, interpretation and execution capabilities for generating,receiving, storing, and/or transmitting information in connection withremote or local services and processes.

Distributed computing provides sharing of computer resources andservices by communicative exchange among computing devices and systems.These resources and services can include the exchange of information,cache storage and disk storage for objects, such as files. Theseresources and services can also include the sharing of processing poweracross multiple processing units for load balancing, expansion ofresources, specialization of processing, and the like. Distributedcomputing takes advantage of network connectivity, allowing clients toleverage their collective power to benefit the entire enterprise. Inthis regard, a variety of devices can have applications, objects orresources that may utilize disclosed and related systems, devices,and/or methods as described for various embodiments of the subjectdisclosure.

FIG. 24 provides a schematic diagram of an exemplary networked ordistributed computing environment. The distributed computing environmentcomprises computing objects 2410, 2412, etc. and computing objects ordevices 2420, 2422, 2424, 2426, 2428, etc., which may include programs,methods, data stores, programmable logic, etc., as represented byapplications 2430, 2432, 2434, 2436, 2438. It can be understood thatobjects 2410, 2412, etc. and computing objects or devices 2420, 2422,2424, 2426, 2428, etc. may comprise different devices, such as PDAs,audio/video devices, mobile phones, MP3 players, personal computers,laptops, etc.

Each object 2410, 2412, etc. and computing objects or devices 2420,2422, 2424, 2426, 2428, etc. can communicate with one or more otherobjects 2410, 2412, etc. and computing objects or devices 2420, 2422,2424, 2426, 2428, etc. by way of the communications network 2440, eitherdirectly or indirectly. Even though illustrated as a single element inFIG. 24, network 2440 may comprise other computing objects and computingdevices that provide services to the system of FIG. 24, and/or mayrepresent multiple interconnected networks, which are not shown. Eachobject 2410, 2412, etc. or 2420, 2422, 2424, 2426, 2428, etc. can alsocontain an application, such as applications 2430, 2432, 2434, 2436,2438, that can make use of an API, or other object, software, firmwareand/or hardware, suitable for communication with or implementation ofdisclosed and related systems, devices, methods, and/or functionalityprovided in accordance with various embodiments of the subjectdisclosure. Thus, although the physical environment depicted may showthe connected devices as computers, such illustration is merelyexemplary, and the physical environment may alternatively be depicted ordescribed comprising various digital devices, any of which can employ avariety of wired and/or wireless services, software objects such asinterfaces, COM objects, and the like.

There are a variety of systems, components, and network configurationsthat support distributed computing environments. For example, computingsystems can be connected by wired or wireless systems, by local networksor widely distributed networks. Currently, many networks are coupled tothe Internet, which can provide an infrastructure for widely distributedcomputing and can encompass many different networks, though any networkinfrastructure can be used for exemplary communications made incident toemploying disclosed and related systems, devices, and/or methods asdescribed in various embodiments.

Thus, a host of network topologies and network infrastructures, such asclient/server, peer-to-peer, or hybrid architectures, can be utilized.The “client” is a member of a class or group that uses the services ofanother class or group to which it is not related. A client can be aprocess, e.g., roughly a set of instructions or tasks, that requests aservice provided by another program or process. The client processutilizes the requested service without having to “know” any workingdetails about the other program or the service itself.

In a client/server architecture, particularly a networked system, aclient is usually a computer that accesses shared network resourcesprovided by another computer, e.g., a server. In the illustration ofFIG. 24, as a non-limiting example, computers 2420, 2422, 2424, 2426,2428, etc. can be thought of as clients and computers 2410, 2412, etc.can be thought of as servers where servers 2410, 2412, etc. provide dataservices, such as receiving data from client computers 2420, 2422, 2424,2426, 2428, etc., storing of data, processing of data, transmitting datato client computers 2420, 2422, 2424, 2426, 2428, etc., although anycomputer can be considered a client, a server, or both, depending on thecircumstances. Any of these computing devices may be processing data,forming metadata, synchronizing data or requesting services or tasksthat may implicate disclosed and related systems, devices, and/ormethods as described herein for one or more embodiments.

A server is typically a remote computer system accessible over a remoteor local network, such as the Internet or wireless networkinfrastructures. The client process can be active in a first computersystem, and the server process can be active in a second computersystem, communicating with one another over a communications medium,thus providing distributed functionality and allowing multiple clientsto take advantage of the information-gathering capabilities of theserver. Any software objects utilized pursuant to disclosed and relatedsystems, devices, and/or methods can be provided standalone, ordistributed across multiple computing devices or objects.

In a network environment in which the communications network/bus 2440 isthe Internet, for example, the servers 2410, 2412, etc. can be Webservers with which the clients 2420, 2422, 2424, 2426, 2428, etc.communicate via any of a number of known protocols, such as thehypertext transfer protocol (HTTP). Servers 2410, 2412, etc. may alsoserve as clients 2420, 2422, 2424, 2426, 2428, etc., as may becharacteristic of a distributed computing environment.

Exemplary Computing Device

As mentioned, advantageously, the techniques described herein can beapplied to devices or systems where it is desirable to employ disclosedand related systems, devices, and/or methods. It should be understood,therefore, that handheld, portable and other computing devices andcomputing objects of all kinds are contemplated for use in connectionwith the various disclosed embodiments. Accordingly, the below generalpurpose remote computer described below in FIG. 25 is but one example ofa computing device. Additionally, disclosed and related systems,devices, and/or methods can include one or more aspects of the belowgeneral purpose computer, such as display, storage, analysis, control,etc.

Although not required, embodiments can partly be implemented via anoperating system, for use by a developer of services for a device orobject, and/or included within application software that operates toperform one or more functional aspects of the various embodimentsdescribed herein. Software can be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by one or more computers, such as client workstations, serversor other devices. Those skilled in the art will appreciate that computersystems have a variety of configurations and protocols that can be usedto communicate data, and thus, no particular configuration or protocolshould be considered limiting.

FIG. 25 thus illustrates an example of a suitable computing systemenvironment 2500 in which one or aspects of the embodiments describedherein can be implemented, although as made clear above, the computingsystem environment 2500 is only one example of a suitable computingenvironment and is not intended to suggest any limitation as to scope ofuse or functionality. Neither should the computing environment 2500 beinterpreted as having any dependency or requirement relating to any oneor combination of components illustrated in the exemplary operatingenvironment 2500.

With reference to FIG. 25, an exemplary remote device for implementingone or more embodiments includes a general purpose computing device inthe form of a computer 2510. Components of computer 2510 can include,but are not limited to, a processing unit 2520, a system memory 2530,and a system bus 2522 that couples various system components includingthe system memory to the processing unit 2520.

Computer 2510 typically includes a variety of computer readable mediaand can be any available media that can be accessed by computer 2510.The system memory 2530 can include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) and/orrandom access memory (RAM). By way of example, and not limitation,memory 2530 can also include an operating system, application programs,other program modules, and program data.

A user can enter commands and information into the computer 2510 throughinput devices 2540. A monitor or other type of display device is alsoconnected to the system bus 2522 via an interface, such as outputinterface 2550. In addition to a monitor, computers can also includeother peripheral output devices such as speakers and a printer, whichcan be connected through output interface 2550.

The computer 2510 can operate in a networked or distributed environmentusing logical connections to one or more other remote computers, such asremote computer 2570. The remote computer 2570 can be a personalcomputer, a server, a router, a network PC, a peer device or othercommon network node, or any other remote media consumption ortransmission device, and can include any or all of the elementsdescribed above relative to the computer 2510. The logical connectionsdepicted in FIG. 25 include a network 2572, such local area network(LAN) or a wide area network (WAN), but can also include othernetworks/buses. Such networking environments are commonplace in homes,offices, enterprise-wide computer networks, intranets and the Internet.

As mentioned above, while exemplary embodiments have been described inconnection with various computing devices and network architectures, theunderlying concepts can be applied to any network system and anycomputing device or system in which it is

Also, there are multiple ways to implement the same or similarfunctionality, e.g., an appropriate API, tool kit, driver code,operating system, control, standalone or downloadable software object,etc. which enables applications and services to use disclosed andrelated systems, devices, methods, and/or functionality. Thus,embodiments herein are contemplated from the standpoint of an API (orother software object), as well as from a software or hardware objectthat implements one or more aspects of disclosed and related systems,devices, and/or methods as described herein. Thus, various embodimentsdescribed herein can have aspects that are wholly in hardware, partly inhardware and partly in software, as well as in software.

Exemplary Mobile Device

FIG. 26 depicts a schematic diagram of an exemplary mobile device 2600(e.g., a mobile handset) that can facilitate various non-limitingaspects of the disclosed subject matter in accordance with theembodiments described herein. Although mobile handset 2600 isillustrated herein, it will be understood that other devices can be amobile device, as described above regarding FIGS. 5, 15, 16, 20-24, forinstance, and that the mobile handset 2600 is merely illustrated toprovide context for the embodiments of the subject matter describedherein. The following discussion is intended to provide a brief, generaldescription of an example of a suitable environment 2600 in which thevarious embodiments can be implemented. While the description includes ageneral context of computer-executable instructions embodied on atangible computer readable storage medium, those skilled in the art willrecognize that the subject matter also can be implemented in combinationwith other program modules and/or as a combination of hardware andsoftware.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of computer readablemedia. Computer readable media can comprise any available media that canbe accessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer readable media can comprise tangible computerreadable storage and/or communication media. Tangible computer readablestorage can include volatile and/or non-volatile media, removable and/ornon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. Tangible computer readable storage caninclude, but is not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD ROM, digital video disk (DVD) or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or any other medium which can be usedto store the desired information and which can be accessed by thecomputer.

Communication media, as contrasted with tangible computer readablestorage, typically embodies computer readable instructions, datastructures, program modules, or other data in a modulated data signalsuch as a carrier wave or other transport mechanism, and includes anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope of computerreadable communications media as distinguishable from computer-readablestorage media.

The handset 2600 can include a processor 2602 for controlling andprocessing all onboard operations and functions. A memory 2604interfaces to the processor 2602 for storage of data and one or moreapplications 2606 (e.g., communications applications such as browsers,apps, etc.). Other applications can support operation of communicationsand/or financial communications protocols. The applications 2606 can bestored in the memory 2604 and/or in a firmware 2608, and executed by theprocessor 2602 from either or both the memory 2604 or/and the firmware2608. The firmware 2608 can also store startup code for execution ininitializing the handset 2600. A communications component 2610interfaces to the processor 2602 to facilitate wired/wirelesscommunication with external systems, e.g., cellular networks, VoIPnetworks, and so on. Here, the communications component 2610 can alsoinclude a suitable cellular transceiver 2611 (e.g., a GSM transceiver)and/or an unlicensed transceiver 2613 (e.g., Wireless Fidelity (WiFi™),Worldwide Interoperability for Microwave Access (WiMax®)) forcorresponding signal communications. The handset 2600 can be a devicesuch as a cellular telephone, a PDA with mobile communicationscapabilities, and messaging-centric devices. The communicationscomponent 2610 also facilitates communications reception fromterrestrial radio networks (e.g., broadcast), digital satellite radionetworks, and Internet-based radio services networks.

The handset 2600 includes a display 2612 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 2612 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 2612 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface2614 is provided in communication with the processor 2602 to facilitatewired and/or wireless serial communications (e.g., Universal Serial Bus(USB), and/or Institute of Electrical and Electronics Engineers (IEEE)2694) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 2600, for example. Audio capabilities areprovided with an audio I/O component 2616, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 2616 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 2600 can include a slot interface 2618 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 2620, and interfacingthe SIM card 2620 with the processor 2602. However, it is to beappreciated that the SIM card 2620 can be manufactured into the handset2600, and updated by downloading data and software.

The handset 2600 can process Internet Protocol (IP) data traffic throughthe communication component 2610 to accommodate IP traffic from an IPnetwork such as, for example, the Internet, a corporate intranet, a homenetwork, a person area network, etc., through an ISP or broadband cableprovider. Thus, VoIP traffic can be utilized by the handset 2600 andIP-based multimedia content can be received in either an encoded or adecoded format.

A video processing component 2622 (e.g., a camera and/or associatedhardware, software, etc.) can be provided for decoding encodedmultimedia content. The video processing component 2622 can aid infacilitating the generation and/or sharing of video. The handset 2600also includes a power source 2624 in the form of batteries and/or analternating current (AC) power subsystem, which power source 2624 caninterface to an external power system or charging equipment (not shown)by a power input/output (I/O) component 2626.

The handset 2600 can also include a video component 2630 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 2630 can facilitate thegeneration, editing and sharing of video. A location-tracking component2632 facilitates geographically locating the handset 2600. A user inputcomponent 2634 facilitates the user inputting data and/or makingselections as previously described. The user input component 2634 canalso facilitate selecting perspective recipients for fund transfer,entering amounts requested to be transferred, indicating accountrestrictions and/or limitations, as well as composing messages and otheruser input tasks as required by the context. The user input component2634 can include such conventional input device technologies such as akeypad, keyboard, mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 2606, a hysteresis component 2636facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with an access point. A softwaretrigger component 2638 can be provided that facilitates triggering ofthe hysteresis component 2638 when a WiFi™ transceiver 2613 detects thebeacon of the access point. A SIP client 2640 enables the handset 2600to support SIP protocols and register the subscriber with the SIPregistrar server. The applications 2606 can also include acommunications application or client 2646 that, among otherpossibilities, can facilitate user interface component functionality asdescribed above.

The handset 2600, as indicated above related to the communicationscomponent 2610, includes an indoor network radio transceiver 2613 (e.g.,WiFi™ transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode Global System for MobileCommunications (GSM) handset 2600. The handset 2600 can accommodate atleast satellite radio services through a handset that can combinewireless voice and digital radio chipsets into a single handheld device.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and/or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a CD, a DVD, a digitaltape, a computer memory, etc.; and a transmission type medium such as adigital and/or an analog communication medium (e.g., a fiber opticcable, a waveguide, a wired communications link, a wirelesscommunication link, etc.).

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into systems. That is, at least a portion ofthe devices and/or processes described herein can be integrated into asystem via a reasonable amount of experimentation. Those having skill inthe art will recognize that a typical system can include one or more ofa system unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control device (e.g., feedback forsensing position and/or velocity; control devices for moving and/oradjusting parameters). A typical system can be implemented utilizing anysuitable commercially available components, such as those typicallyfound in data computing/communication and/or networkcomputing/communication systems.

Various embodiments of the disclosed subject matter sometimes illustratedifferent components contained within, or connected with, othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that, in fact, many other architectures can beimplemented which achieve the same and/or equivalent functionality. In aconceptual sense, any arrangement of components to achieve the sameand/or equivalent functionality is effectively “associated” such thatthe desired functionality is achieved. Hence, any two components hereincombined to achieve a particular functionality can be seen as“associated with” each other such that the desired functionality isachieved, irrespective of architectures or intermediary components.Likewise, any two components so associated can also be viewed as being“operably connected,” “operably coupled,” “communicatively connected,”and/or “communicatively coupled,” to each other to achieve the desiredfunctionality, and any two components capable of being so associated canalso be viewed as being “operably couplable” or “communicativelycouplable” to each other to achieve the desired functionality. Specificexamples of operably couplable or communicatively couplable can include,but are not limited to, physically mateable and/or physicallyinteracting components, wirelessly interactable and/or wirelesslyinteracting components, and/or logically interacting and/or logicallyinteractable components.

With respect to substantially any plural and/or singular terms usedherein, those having skill in the art can translate from the plural tothe singular and/or from the singular to the plural as can beappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for thesake of clarity, without limitation.

It will be understood by those skilled in the art that, in general,terms used herein, and especially in the appended claims (e.g., bodiesof the appended claims) are generally intended as “open” terms (e.g.,the term “including” should be interpreted as “including but not limitedto,” the term “having” should be interpreted as “having at least,” theterm “includes” should be interpreted as “includes, but is not limitedto,” etc.). It will be further understood by those skilled in the artthat, if a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims may containusage of the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limit any particular claim containingsuch introduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, thoseskilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations). Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention (e.g., “asystem having at least one of A, B, and C” would include, but not belimited to, systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). It will be further understood by those skilledin the art that virtually any disjunctive word and/or phrase presentingtwo or more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

In addition, where features or aspects of the disclosure are describedin terms of Markush groups, those skilled in the art will recognize thatthe disclosure is also thereby described in terms of any individualmember or subgroup of members of the Markush group.

As will be understood by one skilled in the art, for any and allpurposes, such as in terms of providing a written description, allranges disclosed herein also encompass any and all possible sub-rangesand combinations of sub-ranges thereof. Any listed range can be easilyrecognized as sufficiently describing and enabling the same range beingbroken down into at least equal halves, thirds, quarters, fifths,tenths, etc. As a non-limiting example, each range discussed herein canbe readily broken down into a lower third, middle third and upper third,etc. As will also be understood by one skilled in the art all languagesuch as “up to,” “at least,” and the like include the number recited andrefer to ranges which can be subsequently broken down into sub-ranges asdiscussed above. Finally, as will be understood by one skilled in theart, a range includes each individual member. Thus, for example, a grouphaving 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, agroup having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells,and so forth.

From the foregoing, it will be noted that various embodiments of thedisclosed subject matter have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the subject disclosure.Accordingly, the various embodiments disclosed herein are not intendedto be limiting, with the true scope and spirit being indicated by theappended claims.

In addition, the words “exemplary” and “non-limiting” are used herein tomean serving as an example, instance, or illustration. For the avoidanceof doubt, the subject matter disclosed herein is not limited by suchexamples. Moreover, any aspect or design described herein as “anexample,” “an illustration,” “exemplary” and/or “non-limiting” is notnecessarily to be construed as preferred or advantageous over otheraspects or designs, nor is it meant to preclude equivalent exemplarystructures and techniques known to those of ordinary skill in the art.Furthermore, to the extent that the terms “includes,” “has,” “contains,”and other similar words are used in either the detailed description orthe claims, for the avoidance of doubt, such terms are intended to beinclusive in a manner similar to the term “comprising” as an opentransition word without precluding any additional or other elements, asdescribed above.

As mentioned, the various techniques described herein can be implementedin connection with hardware or software or, where appropriate, with acombination of both. As used herein, the terms “component,” “system” andthe like are likewise intended to refer to a computer-related entity,either hardware, a combination of hardware and software, software, orsoftware in execution. For example, a component can be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running oncomputer and the computer can be a component. In addition, one or morecomponents can reside within a process and/or thread of execution and acomponent can be localized on one computer and/or distributed betweentwo or more computers.

Systems described herein can be described with respect to interactionbetween several components. It can be understood that such systems andcomponents can include those components or specified sub-components,some of the specified components or sub-components, or portions thereof,and/or additional components, and various permutations and combinationsof the foregoing. Sub-components can also be implemented as componentscommunicatively coupled to other components rather than included withinparent components (hierarchical). Additionally, it should be noted thatone or more components can be combined into a single component providingaggregate functionality or divided into several separate sub-components,and that any one or more middle component layers, such as a managementlayer, can be provided to communicatively couple to such sub-componentsin order to provide integrated functionality, as mentioned. Anycomponents described herein can also interact with one or more othercomponents not specifically described herein but generally known bythose of skill in the art.

As mentioned, in view of the exemplary systems described herein, methodsthat can be implemented in accordance with the described subject mattercan be better appreciated with reference to the flowcharts of thevarious figures and vice versa. While for purposes of simplicity ofexplanation, the methods can be shown and described as a series ofblocks, it is to be understood and appreciated that the claimed subjectmatter is not limited by the order of the blocks, as some blocks canoccur in different orders and/or concurrently with other blocks fromwhat is depicted and described herein. Where non-sequential, orbranched, flow is illustrated via flowchart, it can be understood thatvarious other branches, flow paths, and orders of the blocks, can beimplemented which achieve the same or a similar result. Moreover, notall illustrated blocks can be required to implement the methodsdescribed hereinafter.

While the disclosed subject matter has been described in connection withthe disclosed embodiments and the various figures, it is to beunderstood that other similar embodiments may be used or modificationsand additions may be made to the described embodiments for performingthe same function of the disclosed subject matter without deviatingtherefrom. Still further, multiple processing chips or multiple devicescan share the performance of one or more functions described herein, andsimilarly, storage can be effected across a plurality of devices. Inother instances, variations of process parameters (e.g., configuration,number of components, aggregation of components, process step timing andorder, addition and/or deletion of process steps, addition ofpreprocessing and/or post-processing steps, etc.) can be made to furtheroptimize the provided structures, devices and methods, as shown anddescribed herein. In any event, the systems, structures and/or devices,as well as the associated methods described herein have manyapplications in various aspects of the disclosed subject matter, and soon. Accordingly, the invention should not be limited to any singleembodiment, but rather should be construed in breadth, spirit and scopein accordance with the appended claims.

What is claimed is:
 1. A method, comprising: storing, by a devicecomprising a processor, personal information associated with a user in adistributed file system (DFS); creating, by the device, a plurality ofblock chains of personal information, based at least in part on adetermined category of use of each of the plurality of block chains;wherein the storing the personal information comprises encrypting, viathe device, the personal information with supplemental information tofacilitate at least one of creation of at least one block chain of theplurality of block chains or determining an applicability status of arequest for authorization, wherein the encrypting the personalinformation with supplemental information comprises encrypting, via thedevice, either a cryptographic hash of a prior block of personalinformation in the at least one block chain or a link to the prior blockof personal information in the at least one block chain stored in theDFS; and transmitting an authorization, by the device, to access a setof the plurality of block chains based on the determined category of useassociated with a request for authorization.
 2. The method of claim 1,wherein the storing the personal information in DFS comprises storing,via the device, the personal information in inter-planetary file system(IPFS).
 3. The method of claim 1, wherein the encrypting the personalinformation with supplemental information further comprises encrypting,via the device, at least one of a verifying entity associated with thepersonal information, a digital signature associated with the verifyingentity, information associated with an encryption key or decryption key,or other authorization information associated with the set of theplurality of block chains.
 4. The method of claim 4, wherein theencrypting the link to the prior block of personal information in the atleast one block chain comprises encrypting, via the device, an encryptedlink to the prior block of personal information in the at least oneblock chain.
 5. The method of claim 4, wherein the encrypting the otherauthorization information associated with the set of the plurality ofblock chains comprises encrypting, via the device, at least one term ofuse determined by the user.
 6. The method of claim 1, wherein thecreating the plurality of block chains of personal information comprisesdetermining, via the device, whether the personal information ispersonally identifying information or other personal information,wherein the personally identifying information is defined as informationor combinations of information that resolve to a unique user, meeting orexceeding a predetermined threshold confidence level, and wherein theother personal information is defined as other information orcombinations of other information that does not resolve to the uniqueuser, by failing to meet or exceed the predetermined thresholdconfidence level, and creating the plurality of block chains based on atleast the personally identifying information.
 7. The method of claim 1,further comprising: receiving, via the device, the request forauthorization; determining, via the device, from the request forauthorization the determined category of use; determining, via thedevice, whether at least one responsive block chain exists that isresponsive to the determined category of use and the request forauthorization in the set of the plurality of block chains; creating, viathe device, the at least one responsive block chain if the at least oneresponsive block chain does not exist; and transmitting theauthorization comprising transmitting, via the device, at least onecryptographic hash associated with a last block of the at least oneresponsive block chain and a link to the last block of the at least oneresponsive block chain stored in the DFS.
 8. A system, comprising aprocessor and a memory that stores computer executable components that,when executed by the processor, facilitate performance of operations,the computer executable components comprising: a storage componentconfigured to store personal information associated with a user in adistributed file system (DFS); a data management component configured tocreate a plurality of block chains of personal information, based atleast in part on a determined category of use of each of the pluralityof block chains; wherein the storage component is further configured tostore the personal information with supplemental information encryptedto facilitate at least one of creation of at least one block chain ofthe plurality of block chains or determining an applicability status ofa request for authorization; wherein the data management component isassociated with a cryptographic component configured to encrypt either aplurality of a cryptographic hash of a prior block of personalinformation in the at least one block chain or a link to the prior blockof personal information in the at least one block chain stored in theDFS; and an authorization component configured to transmit anauthorization to access a set of the plurality of block chains based onthe determined category of use associated with the request forauthorization.
 9. The system of claim 11, wherein the storage componentis further configured to store the personal information in the DFScomprising inter-planetary file system (IPFS).
 10. The system of claim11, wherein the data management component is associated with acryptographic component configured to encrypt at least one of averifying entity associated with the personal information, a digitalsignature associated with the verifying entity, information associatedwith an encryption key or decryption key, or other authorizationinformation associated with the set of the plurality of block chains.11. The system of claim 14, wherein the link to the prior block ofpersonal information in the at least one block chain comprises anencrypted link to the prior block of personal information in the atleast one block chain.
 12. The system of claim 14, wherein the otherauthorization information associated with the set of the plurality ofblock chains comprises at least one term of use determined by the user,wherein the at least one term of use comprises an expiration term for atleast one of the authorization or the personal information.
 13. Thesystem of claim 16, wherein the data management component is furtherconfigured to determine the at least one term of use, further comprisingat least one of a validity term associated with the personalinformation, at least one of a payee or a requested fee associated withthe at least one of the authorization or the personal information, atleast one of a transmission limit or a storage limit associated with theat least one of the authorization or the personal information, or arestriction associated with the at least one of the authorization or thepersonal information on a third party.
 14. The system of claim 11,wherein the data management component is further configured to determinewhether the personal information is personally identifying informationor other personal information, wherein the personally identifyinginformation is defined as information or combinations of informationthat resolve to a unique user, meeting or exceeding a predeterminedthreshold confidence level, and wherein the other personal informationis defined as other information or combinations of other informationthat does not resolve to the unique user, by failing to meet or exceedthe predetermined threshold confidence level, and is further configuredto create the plurality of block chains based on at least the personallyidentifying information.
 15. A non-transitory machine-readable storagemedium, comprising executable instructions that, when executed by adevice comprising processor, facilitate performance of operations,comprising: storing, by the device, personal information associated witha user in a distributed file system (DFS); creating, by the device, aplurality of block chains of personal information, based at least inpart on a determined category of use of each of the plurality of blockchains; encrypting, via the device, the personal information withsupplemental information to facilitate at least one of creation of atleast one block chain of the plurality of block chains or determining anapplicability status of the request for authorization, wherein thesupplemental information comprises at least one of a cryptographic hashof a prior block of personal information in the at least one block chainor a link to the prior block of personal information in the at least oneblock chain stored in the DFS; and transmitting an authorization, by thedevice, to access a set of the plurality of block chains based on thedetermined category of use associated with a request for authorization.16. The non-transitory machine-readable storage medium of claim 21, theoperations further comprising: storing, via the device, the personalinformation in inter-planetary file system (IPFS).
 17. Thenon-transitory machine-readable storage medium of claim 21, theoperations further comprising: encrypting, via the device, at least oneof a verifying entity associated with the personal information, adigital signature associated with the verifying entity, informationassociated with an encryption key or decryption key, or otherauthorization information associated with the set of the plurality ofblock chains.